@AnimaApp
Basic information
Connect AI coding agents to Anima Playground, Figma designs, and your team's design system. Bridge the gap between prototypes and production code.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"anima": {
"url": "https://public-api.animaapp.com/v1/mcp"
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list directly from this server's endpoint using the button above.
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.
Connect Claude Desktop to your ServiceNow PDI. Query records, inspect Business Rules, review ACLs, and troubleshoot against your live instance.
TruVerifAI's Panel Review is the guardian agent for AI's highest-stakes coding decisions: four frontier models argue over an AI coding agent's riskiest designs, diffs, and commits before they execute, with local review g
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
BERGHAIN MCP server — sovereign AI stress-testing mcp / ai / multi-agent / adversarial / stress-test / claude
AI growth agent for software businesses. Ranla ships pages that rank on Google, gets your product named in AI answers, replies on Reddit and sends lifecycle email. Ask how growth is going, have Ranla draft the work and a
Comments