Anthill Cloud MCP server
Early accessUse Anthill Cloud from the AI tools your teams already use. Connect Claude to your organization's tactics, artifacts and assets over the Model Context Protocol.
The server is a remote MCP endpoint. Every call goes through the same Anthill Cloud APIs the apps use, as the person who signed in, so your organization and your permissions apply to every request.
Server URL
Add this URL to your tool. It is the same for everyone; your sign-in decides which organization you reach.
https://mcp.dev.cloud.anthill.technology/mcp
Prerequisites
Connect your tool
Choose the tool you are connecting. Each needs only the server URL; you sign in the first time you use it.
Claude Code Available
Add the server once; Claude Code keeps your sign-in and refreshes it.
- 1Run the command below in a terminal.
- 2In Claude Code, run
/mcp, chooseanthill-cloudand select Authenticate. - 3Enter your organization's short name, sign in, and accept the consent screen.
claude mcp add --transport http anthill-cloud https://mcp.dev.cloud.anthill.technology/mcp
Claude.ai and Desktop Coming soon
Works in Claude.ai, Claude Desktop and the Claude mobile apps once added.
- 1Open Settings, then Connectors, and choose Add custom connector.
- 2Name it Anthill Cloud and paste the server URL.
- 3Select Connect, enter your organization's short name, sign in, and accept the consent screen.
https://mcp.dev.cloud.anthill.technology/mcp
VS Code Coming soon
GitHub Copilot in VS Code can use the tools in agent mode.
- 1Run
MCP: Add Serverfrom the command palette, choose HTTP and paste the server URL - or add the configuration below to.vscode/mcp.json. - 2Start the server and sign in when VS Code asks.
{
"servers": {
"anthill-cloud": {
"type": "http",
"url": "https://mcp.dev.cloud.anthill.technology/mcp"
}
}
}Microsoft Copilot Studio Planned
Connecting Microsoft Copilot Studio agents is planned. Talk to your Anthill contact if you need it.
Cursor Planned
Cursor support is planned once its sign-in method is confirmed against ours.
Signing in
You sign in as yourself, with your usual Anthill Cloud account. There is no shared key to distribute and nothing for an administrator to issue.
- 1Organization. Enter your organization's short name. This comes before your credentials.
- 2Sign in. Use your usual Anthill Cloud sign-in.
- 3Approve. Anthill Cloud asks whether your tool may access your account. Choose Accept.
Tools
Every tool reads, returns only what you can see, and pages its results. Tool names may change before general availability.
getAomTactics
Read
getAomArtifacts
Read
getAomAssets
Read
Security and governance
The answers your security team will ask for in a vendor assessment.
Example prompts
Once connected, ask in plain language. Your tool picks the right Anthill tool.
What's next
Later rounds extend the same server. Timing follows the platform work each one depends on.
Troubleshooting
"Oops!, something went wrong" after entering the organization
Your organization has not been enabled for AI assistants yet. Contact support with your organization's short name.
"No connections enabled for the organization are visible"
Your organization is not set up for this sign-in method yet. Contact support with your organization's short name.
Claude Code says it got new credentials but the server rejected them
Remove the server and add it again - claude mcp remove anthill-cloud - then repeat the steps above.
Signed in, but a tool returns nothing
Tools return only what your account can see in that organization. Check the same view in Anthill Cloud.
Still stuck? Contact Anthill support with your organization's short name.