amodb-mcp
OfficialRelated Servers
Alternatives to amodb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents, and to build automations through natural language. It also includes an OpenAPI codegen that turns any OpenAPI spec into MCP tools.1,264 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to list and manage workspaces, projects, tasks, AI agents, and automations through a hosted OAuth-secured endpoint or a local stdio package. Also generates MCP tools from any OpenAPI spec.1,264 npmMIT
- AlicenseNot gradedqualityAmaintenanceExposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible applications to manage local and cloud language models, run text generation and chat, generate embeddings, and perform web search and content fetching.561 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceExposes search, locate, expand, and find_related tools over MCP so AI coding agents in Claude Code, Cursor, Copilot, and other clients can retrieve the best code chunks (path, lines, snippet) by meaning instead of grep or glob. This hybrid code search lets agents find the right files in fewer steps, using up to 50% fewer tokens.296 npm12MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language, using a hosted OAuth-authenticated endpoint or a local stdio package. It also ships an OpenAPI codegen tool for generating MCP tools from any OpenAPI spec.1,264 npmMIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct input type and resource: name search, id-based detail retrieval, external-id lookup, trending, filter discovery, and cinema showtimes. Overlaps such as search_titles versus discover_movies are explicitly separated by description (name vs. filters), so misselection is unlikely.
Eight of nine tools follow a consistent snake_case verb_noun or verb_preposition_noun pattern (search_titles, get_movie, get_tv_show, find_by_external_id, etc.). 'trending' is a lone noun without a verb, but it is still readable and no mixed conventions appear.
Nine tools is well within the effective range for a read-only media metadata API. Each tool covers a distinct capability, with no obvious filler or redundancy.
The surface covers the core read lifecycle: search, detail by id, external-id fallback, trending, filter discovery, seasons/episodes, people, and showtimes. A TV-specific discover tool and standalone episode-by-id lookup are missing, but agents can work around these via get_tv_show and get_season.