agentswitchboard
Server Details
Search a curated directory of 300+ verified AI agents, MCP servers, and agentic tools.
- Status
- Healthy
- Uptime
- 100.0% over 57 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- assafbar2/agentswitchboard.dev
- GitHub Stars
- 0
- Server Listing
- agentSwitchBoard
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search for discovery, get_agent for full details of a specific slug, and list_categories for browse/filter navigation. There is no meaningful overlap between the three.
All tool names follow a consistent lowercase verb_noun pattern: get_agent, list_categories, search_agents. The singular/plural usage matches the tool's return semantics, so naming is predictable and clear.
Three tools is a lean but well-scoped set for a read-only directory. Each tool maps to a distinct stage in the discovery workflow—search, browse categories, and retrieve details—with no redundant or filler tools.
The core directory workflow is covered: search agents, list categories to browse, and get full agent details. The only minor gap is the lack of an explicit list-all or paginated browsing tool, though search with category filters likely covers most discovery needs.
Available Tools
3 toolsget_agentGet Agent DetailsInspect
Full detail for one agent by slug: skills, auth, streaming/push support, tags, provider links.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Agent slug, e.g. "playwright-mcp" |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| name | Yes | |
| slug | Yes | |
| tags | Yes | |
| skills | Yes | |
| addedAt | No | |
| agentUrl | Yes | |
| authType | Yes | |
| official | Yes | First-party listing from a major vendor |
| provider | Yes | |
| verified | Yes | |
| categories | Yes | |
| description | Yes | |
| providerUrl | Yes | |
| accessMethods | Yes | |
| officialVendor | Yes | |
| supportsStreaming | Yes | |
| supportsPushNotifications | Yes |
list_categoriesList CategoriesAInspect
All directory categories with live agent counts. Slugs are valid inputs for search_agents.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| categories | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It discloses that counts are live and that slugs are usable, which adds value. However, it does not mention any side effects, error conditions, or whether the operation is read-only, leaving some behavioral aspects undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero filler. The primary purpose is front-loaded, and the usage hint is a single, focused addition. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and an existing output schema, the description is sufficient for an agent to invoke the tool correctly. It states what is returned (categories with live counts) and how to use the results (slugs for search_agents), leaving no critical gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is nothing to explain beyond the schema. Baseline 4 applies per the rubric since no parameters need semantic elaboration.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: lists all directory categories, with the added detail of live agent counts. This clearly distinguishes it from siblings get_agent (single agent) and search_agents (search operation), so an agent can immediately tell it apart.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage by noting that slugs are valid inputs for search_agents, which suggests a workflow: first list categories, then use slugs in searches. It does not explicitly contrast with get_agent, but the purpose is clear enough that an agent would know when to call it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_agentsSearch AgentsInspect
Search the Agent Switchboard directory of vetted AI agents, MCP servers, and agentic tools. Returns relevance-ranked matches. Filter by category slug, access methods, and/or official (first-party listings from major vendors).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per page (1–50) | |
| query | No | Free-text search (name, description, skills, tags) | |
| access | No | Require ALL of these access methods (api, mcp, cli, browser-extension) | |
| offset | No | Number of results to skip, for pagination | |
| category | No | Category slug, e.g. "code-devtools", "voice-messaging" | |
| official | No | Only first-party listings from major vendors (e.g. Notion's own Notion MCP) |
Output Schema
| Name | Required | Description |
|---|---|---|
| limit | Yes | |
| total | Yes | Total matches before paging |
| agents | Yes | |
| offset | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
get_agent3 fields changed- added
Output schema / properties / officialAdded value: +{ + "description": "First-party listing from a major vendor", + "type": "boolean" +} - added
Output schema / properties / officialVendorAdded value: +{ + "type": [ + "string", + "null" + ] +} - changed
Output schema / requiredPrevious value: -[ - "name", - "slug", - "description", - "provider", - "categories", - "accessMethods", - "authType", - "verified", - "url", - "agentUrl", - "providerUrl", - "skills", - "tags", - "supportsStreaming", - "supportsPushNotifications" -]New value: +[ + "name", + "slug", + "description", + "provider", + "categories", + "accessMethods", + "authType", + "verified", + "official", + "officialVendor", + "url", + "agentUrl", + "providerUrl", + "skills", + "tags", + "supportsStreaming", + "supportsPushNotifications" +]
- Changed
search_agents4 fields changed- added
Input schema / properties / officialAdded value: +{ + "description": "Only first-party listings from major vendors (e.g. Notion's own Notion MCP)", + "type": "boolean" +} - added
Output schema / properties / agents / items / properties / officialAdded value: +{ + "description": "First-party listing from a major vendor", + "type": "boolean" +} - added
Output schema / properties / agents / items / properties / officialVendorAdded value: +{ + "type": [ + "string", + "null" + ] +} - changed
Output schema / properties / agents / items / requiredPrevious value: -[ - "name", - "slug", - "description", - "provider", - "categories", - "accessMethods", - "authType", - "verified", - "url" -]New value: +[ + "name", + "slug", + "description", + "provider", + "categories", + "accessMethods", + "authType", + "verified", + "official", + "officialVendor", + "url" +]
1 tool update
- Changed
search_agents6 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Max results per page (1–50)" - added
Input schema / properties / offsetAdded value: +{ + "default": 0, + "description": "Number of results to skip, for pagination", + "minimum": 0, + "type": "integer" +} - added
Output schema / properties / limitAdded value: +{ + "type": "integer" +} - added
Output schema / properties / offsetAdded value: +{ + "type": "integer" +} - added
Output schema / properties / total / descriptionAdded value: +"Total matches before paging" - changed
Output schema / requiredPrevious value: -[ - "total", - "agents" -]New value: +[ + "total", + "offset", + "limit", + "agents" +]
3 tool updates
- Changed
get_agent1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "accessMethods": { + "items": { + "type": "string" + }, + "type": "array" + }, + "addedAt": { + "type": "string" + }, + "agentUrl": { + "type": "string" + }, + "authType": { + "type": "string" + }, + "categories": { + "items": { + "type": "string" + }, + "type": "array" + }, + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "provider": { + "type": "string" + }, + "providerUrl": { + "type": "string" + }, + "skills": { + "items": { + "additionalProperties": true, + "properties": { + "description": { + "type": "string" + }, + "id": { + "type": "string" + }, + "name": { + "type": "string" + } + }, + "required": [ + "id", + "name", + "description" + ], + "type": "object" + }, + "type": "array" + }, + "slug": { + "type": "string" + }, + "supportsPushNotifications": { + "type": "boolean" + }, + "supportsStreaming": { + "type": "boolean" + }, + "tags": { + "items": { + "type": "string" + }, + "type": "array" + }, + "url": { + "type": "string" + }, + "verified": { + "type": "boolean" + } + }, + "required": [ + "name", + "slug", + "description", + "provider", + "categories", + "accessMethods", + "authType", + "verified", + "url", + "agentUrl", + "providerUrl", + "skills", + "tags", + "supportsStreaming", + "supportsPushNotifications" + ], + "type": "object" +}
- Changed
list_categories1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "categories": { + "items": { + "additionalProperties": false, + "properties": { + "agentCount": { + "type": "number" + }, + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "slug": { + "type": "string" + } + }, + "required": [ + "slug", + "name" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "categories" + ], + "type": "object" +}
- Changed
search_agents1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "agents": { + "items": { + "additionalProperties": false, + "properties": { + "accessMethods": { + "items": { + "type": "string" + }, + "type": "array" + }, + "authType": { + "type": "string" + }, + "categories": { + "items": { + "type": "string" + }, + "type": "array" + }, + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "provider": { + "type": "string" + }, + "slug": { + "type": "string" + }, + "url": { + "type": "string" + }, + "verified": { + "type": "boolean" + } + }, + "required": [ + "name", + "slug", + "description", + "provider", + "categories", + "accessMethods", + "authType", + "verified", + "url" + ], + "type": "object" + }, + "type": "array" + }, + "total": { + "type": "integer" + } + }, + "required": [ + "total", + "agents" + ], + "type": "object" +}
3 tool updates
- First observed
get_agent - First observed
list_categories - First observed
search_agents
Related MCP Connectors
Search a curated directory of AI tools, AI agents and MCP servers by task, pricing and platform.
Search a curated directory of agent tools, MCP servers, APIs, protocols and skills. No auth.
Find MCP servers, skills, plugins, agents, prompts and rules for any task.
AI tool directory MCP server, live since July 2026. Tools, agents, models, companies, services.
Related MCP Servers
- AlicenseAqualityCmaintenanceMCP server that searches 3,800+ open-source AI agents by capability, ranked by real traction (stars, activity). Query it from Claude Desktop, Cursor, Cline, or Windsurf.353 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn app store for AI agents. Discover, search, and install 49+ MCP servers from a curated catalog.9 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to search a directory of 13,870+ MCP servers, 4,384+ agent skills, and plugins from Remote OpenClaw, returning install commands directly.352 npm6MIT
- FlicenseNot gradedqualityDmaintenanceFinds the right MCP server for a task from over 1,400 indexed servers ranked by community trust. Also provides outcome-ranked web search for AI agents with no API key or rate limits.4-
Glama MCP Gateway
Add one secure layer between your agents and this server.