Answer: Verify the server correctly implements the MCP protocol's `tools/list` method; for STDIO servers, ensure the process writes valid JSON-RPC messages to stdout and reads from stdin, since logging or debug output to stdout will break the protocol; and check that environment variables are set correctly, as missing values (e.g., a blank API key) can cause the server to start but fail to register tools. Status: Confirmed Entry: tool/devin/troubleshooting/mcp-tools-not-available Revision: 4 Digest: sha256:575ffad998a6ae0f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:17:03Z Last changed: 2026-11-20T12:50:08Z (Example missing value: — → a blank API key) Last verified: 2026-11-20T12:50:08Z Next check: 2026-11-21T12:50:08Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Protocol method to verify | tools/list | [1] | 2026-11-20 STDIO stdout requirement | valid JSON-RPC messages to stdout | [1] | 2026-11-20 STDIO stdin requirement | reads from stdin | [1] | 2026-11-20 What breaks the protocol | logging or debug output to stdout will break the protocol | [1] | 2026-11-20 Environment variable check | Check that environment variables are set correctly. | [1] | 2026-11-20 Example missing value | a blank API key | [1] | 2026-11-20 Sources: [1] Cognition. "Devin MCP servers and marketplace". https://docs.devin.ai/work-with-devin/mcp.md Role: primary. Accessed: 2026-11-20T12:50:08Z Quote: "Verify the server correctly implements the MCP protocol's `tools/list` method." (Supports: Protocol method to verify) Quote: "For STDIO servers, ensure the process writes valid JSON-RPC messages to stdout and reads from stdin" (Supports: STDIO stdout requirement, STDIO stdin requirement) Quote: "logging or debug output to stdout will break the protocol" (Supports: What breaks the protocol) Quote: "Check that environment variables are set correctly." (Supports: Environment variable check) Quote: "Missing values (e.g., a blank API key) can cause the server to start but fail to register tools." (Supports: Example missing value) Published: 2026-11-20T09:41:38Z Snapshot SHA-256: 78189f5cbf262658c0aacba3d8417e417331e1e04f26e35ab7b0e64507044933 (captured 2026-11-20T12:50:06Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:50:08Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:50:08Z Last attempt: 2026-11-20T12:50:08Z Notes and limitations: Extracted automatically from a single official source (section "Server connects but tools aren't available"). Related: https://latestn.com/tool/devin/troubleshooting/model-allowlist-etag-412 Why does the Devin Desktop model allowlist update return a 412 error and how do I fix it? https://latestn.com/tool/devin/troubleshooting/permanent-inotify-limit-fix How do I permanently increase inotify watch limits for Devin Desktop on Linux? https://latestn.com/tool/devin/troubleshooting/preview-sleeping-sessions What happens to Devin browser previews when a session goes to sleep? https://latestn.com/tool/devin/troubleshooting/insights-troubleshooting How do I troubleshoot when no insights are available or analysis takes too long in Devin Session Insights? https://latestn.com/tool/devin/troubleshooting/jetbrains-plugin-maintenance-mode Is the Windsurf JetBrains plugin still supported, or should I switch to Devin ACP? https://latestn.com/tool/devin/troubleshooting/macos-limitations What are the limitations of Devin macOS support? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:50:08Z | changed | Example missing value: — → a blank API key | [1] 2026-11-20T12:50:08Z | changed | Environment variable check: — → Check that environment variables are set correctly. | [1] 2026-11-20T12:50:08Z | changed | What breaks the protocol: — → logging or debug output to stdout will break the protocol | [1] 2026-11-20T12:50:08Z | changed | STDIO stdin requirement: — → reads from stdin | [1] 2026-11-20T12:50:08Z | changed | STDIO stdout requirement: — → valid JSON-RPC messages to stdout | [1] 2026-11-20T12:50:08Z | changed | Protocol method to verify: — → tools/list | [1] 2026-11-20T12:50:08Z | changed | missing values example: a blank API key → — | [1] 2026-11-20T12:50:08Z | changed | environment variables: Check that environment variables are set correctly. → — | [1] 2026-11-20T12:50:08Z | changed | stdout warning: logging or debug output to stdout will break the protocol → — | [1] 2026-11-20T12:50:08Z | changed | STDIO requirement: valid JSON-RPC messages → — | [1] 2026-11-20T12:50:08Z | changed | protocol method: tools/list → — | [1] 2026-11-19T12:43:55Z | changed | missing values example: — → a blank API key | [1] 2026-11-19T12:43:55Z | changed | environment variables: — → Check that environment variables are set correctly. | [1] 2026-11-19T12:43:55Z | changed | stdout warning: — → logging or debug output to stdout will break the protocol | [1] 2026-11-19T12:43:55Z | changed | STDIO requirement: — → valid JSON-RPC messages | [1] 2026-11-19T12:43:55Z | changed | protocol method: — → tools/list | [1] 2026-11-19T12:43:55Z | changed | Missing value example: a blank API key → — | [1] 2026-11-19T12:43:55Z | changed | Environment variable check: Check that environment variables are set correctly. → — | [1] 2026-11-19T12:43:55Z | changed | STDIO breakage cause: logging or debug output to stdout will break the protocol → — | [1] 2026-11-19T12:43:55Z | changed | STDIO output requirement: valid JSON-RPC messages to stdout → — | [1] 2026-11-19T12:43:55Z | changed | Protocol method to verify: tools/list → — | [1] 2026-11-15T12:53:38Z | changed | Missing value example: — → a blank API key | [1] 2026-11-15T12:53:38Z | changed | Environment variable check: — → Check that environment variables are set correctly. | [1] 2026-11-15T12:53:38Z | changed | STDIO breakage cause: — → logging or debug output to stdout will break the protocol | [1] 2026-11-15T12:53:38Z | changed | STDIO output requirement: — → valid JSON-RPC messages to stdout | [1] 2026-11-15T12:53:38Z | changed | Protocol method to verify: — → tools/list | [1] 2026-11-15T12:53:38Z | changed | environment variable issue example: a blank API key → — | [1] 2026-11-15T12:53:38Z | changed | STDIO stdout warning: logging or debug output to stdout will break the protocol → — | [1] 2026-11-15T12:53:38Z | changed | STDIO stdout requirement: valid JSON-RPC messages → — | [1] 2026-11-15T12:53:38Z | changed | protocol method to verify: tools/list → — | [1] 2026-11-13T03:17:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/troubleshooting/mcp-tools-not-available/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/troubleshooting/mcp-tools-not-available POST: https://latestn.com/dispute/tool/devin/troubleshooting/mcp-tools-not-available with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/troubleshooting/mcp-tools-not-available?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot a Devin MCP server that connects but tools aren't available? Revision 4, last verified 2026-11-20T12:50:08Z. https://latestn.com/tool/devin/troubleshooting/mcp-tools-not-available (accessed 2026-11-21T10:02:35Z). @misc{LatestN_tool_devin_troubleshooting_mcp_tools_not_available_r4, title = {How do I troubleshoot a Devin MCP server that connects but tools aren't available?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/troubleshooting/mcp-tools-not-available}}, note = {Revision 4; digest sha256:575ffad998a6ae0f; last verified 2026-11-20T12:50:08Z; accessed 2026-11-21T10:02:35Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/troubleshooting/mcp-tools-not-available