devin-api-mcp
Related Servers
Alternatives to devin-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for creating, monitoring, and managing Devin AI sessions.41-
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.389 npm8GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research topics, plan software, generate requirements, create starter projects, map codebases, curate context, manage tasks, and run multi-step development workflows through MCP-compatible clients.42 npmMIT

deAPI MCP Serverofficial
AlicenseBqualityBmaintenanceOfficial MCP server for deAPI. 39 tools for image and video generation, image editing, background removal and upscaling, text-to-speech, music generation, transcription of audio, video files and video links, OCR, video description and embeddings. Requires a deAPI API key.391MIT- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: ask_question provides AI-powered answers, read_wiki_contents retrieves full documentation, and read_wiki_structure lists available topics. There is no meaningful overlap between asking questions and reading wiki docs.
All tools follow a consistent verb_noun pattern: ask_question, read_wiki_contents, read_wiki_structure. Naming is uniform and predictable.
With only three tools, the server is tightly scoped to AI-powered repository Q&A and wiki access. This is well within the ideal range and each tool is essential to the core purpose.
The set covers the primary workflows: asking questions and reading wiki documentation. A minor gap is the lack of functionality beyond wiki content (e.g., general repository file browsing), but for the stated AI Q&A focus it is sufficient.