@AnimaApp
基本情報
Connect AI coding agents to Anima Playground, Figma designs, and your team's design system. Bridge the gap between prototypes and production code.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"anima": {
"url": "https://public-api.animaapp.com/v1/mcp"
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。
The AgentGrid.io MCP Server connects AI coding tools and autonomous agents to your AgentGrid.io workspace.
It allows people and agents to create, read, and update the same live artifacts, including apps, documents, reports, and other files, without passing copies back and forth.
Every artifact has a stable URL and a complete version history showing who changed what. Each connected agent has its own identity and receives only the permissions you grant.
Add the server to an MCP-compatible client, such as Claude Code, Cursor, or Windsurf, using this configuration:
{
"mcpServers": {
"agentgrid": {
"type": "http",
"url": "https://api.agentgrid.io/v1/mcp"
}
}
}
Complete the browser sign-in when prompted, then select the team and permissions the agent should receive.
Once connected, ask the agent to create a new artifact or continue working on an existing AgentGrid.io artifact.
Confirm that the agent is connected to the team that owns the artifact and has permission to read it. AgentGrid.io artifacts belong to teams, so an agent connected to a different team will not be able to access them.
Check that the server URL is exactly: ```text https://api.agentgrid.io/v1/mcp ``` Make sure your client supports remote MCP servers over Streamable HTTP. After changing the configuration, restart the MCP client.
Remove and reconnect the AgentGrid.io MCP Server, then complete the browser approval flow again. Make sure you select the correct team and grant the permissions the agent needs.
A connected agent can create artifacts and perform the actions you approve, such as reading, updating, sharing, or publishing. An agent cannot exceed either its granted permissions or the permissions of the person who connected it.
Yes. Multiple agents can work on the same AgentGrid.io artifact. Each agent has its own identity, and its changes appear under its name in the artifact’s version history.
Yes. Open **Share → Manage access** in AgentGrid.io and remove the agent. Its access will be revoked immediately, while its previous contributions will remain in the artifact’s history.
For native MCP access, you only need: * An MCP-compatible client * An AgentGrid.io account * An internet connection The MCP server runs remotely, so no local AgentGrid.io runtime is required.
No. **Sharing** gives selected people or agents access to an artifact. **Publishing** deploys an artifact to a public URL that anyone can open. Publishing is a separate action and should happen only when explicitly requested.
Agent skill: turn what your AI assistant knows about you into a personalized hypnosis session on hypnothera.ai
FACTANKER serves 1.18B+ evidence-backed facts about US companies, banks, nonprofits and federal spending, sourced from SEC EDGAR, FFIEC call reports, IRS 990 filings and USAspending. Every value carries its evidence: fil
NetFoundry LLM Gateway is an OpenAI-compatible API proxy that routes requests across multiple LLM providers using zero-trust networking. Zero trust LLM gateway. OpenAI-compatible proxy with semantic routing and load bala
MCP-native LLM councils for debates, juries, blind panels, voting, refinement, and custom multi-model deliberation.
scvd.store is an evidence observatory for agentic commerce. Independent signed observation of what other people's endpoints, artifacts and payments actually did among other things. USDC on Base, Arbitrum One, World Chain
コメント