AgentAtlas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTATLAS_MCP_URL | No | Overrides the endpoint the local stdio bridge forwards JSON-RPC to. Defaults to https://agentatlas.dev/api/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_atlasB | Search AgentAtlas, the verified map of the AI agent stack: setup guides for coding agents (Claude Code, Codex, Cursor, Gemini CLI, Copilot and more), official MCP servers, plugin systems, eval frameworks, agent benchmarks and protocols. Every entry is sourced from vendor docs. |
| get_guideB | Get a full sourced setup guide (settings, commands, config files) by slug, as Markdown with source links. |
| get_mcp_serverB | Get install commands for Claude Code, Codex, Gemini CLI, Cursor and VS Code, plus tools and auth details, for an official MCP server by slug. |
| get_pricingA | Get coding agent plans and prices copied from vendor pricing pages. Optional harness slug, e.g. 'cursor' or 'claude-code'. |
| get_setup_configA | Get ready-to-write MCP config for one client and one or more official MCP servers, with the file path to write it to. Clients: claude-code, claude-code-cli, cursor, vs-code, codex, gemini-cli, antigravity, copilot-cli, claude-desktop, opencode, cline, kiro, zed, devin-desktop, amp. Use search_atlas (type mcp_server) to find server slugs. |
| get_trendingB | What is trending in AI agents: fastest-rising new agent and MCP repos on GitHub, stars gained by tracked agent projects, most-discussed agent posts on Hacker News, and verified accounts to follow. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource type (guide, mcp server, pricing, setup config, trending), and descriptions clarify that get_mcp_server returns install/auth info while get_setup_config composes writable client config from server slugs. There is mild overlap between get_guide and get_mcp_server setup content, and get_setup_config depends on the other two, but an agent can still route queries correctly.
All six tools follow a clean verb_noun snake_case pattern (search_atlas, get_guide, get_mcp_server, get_pricing, get_setup_config, get_trending). The single search verb plus uniform get_* modifiers makes the surface highly predictable.
Six tools is well-scoped for a read-only reference/knowledge server, with one discovery tool plus focused retrievers. No tool feels redundant or missing at this scale.
Search plus slug-based retrieval covers guides, MCP servers, pricing, config generation, and trending, which is solid lifecycle coverage for a documentation atlas. Minor gaps: no browse/list-by-type tool (e.g. enumerate all MCP servers or clients) and no way to list available slugs without relying on search.