mcpbeat

Developer Tools MCP Server

goog.workspace-developer/developer-tools
answering

Developer Tools is answering right now. Last checked 12 min ago. It exposes 2 tools.

Provides tools for searching Google Workspace documentation and much more.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
283 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add developer-tools --transport http https://workspace-developer.goog/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "developer-tools": {
      "url": "https://workspace-developer.goog/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.developer-tools]
url = "https://workspace-developer.goog/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "developer-tools": {
      "url": "https://workspace-developer.goog/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "developer-tools": {
      "url": "https://workspace-developer.goog/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

workspace
fetch_workspace_docs
Fetches the content of a Google Workspace documentation page such as those returned by the `search_workspace_docs` tool.
search_workspace_docs
Searches the latest official Google Workspace documentation, including API references, conceptual guides, tutorials, and code examples.

Endpoints

URLTransportStateLatencyChecked
https://workspace-developer.goog/mcp streamable-http answering 221 ms 12 min ago

Developer Tools — questions

Answers built from our own checks of this server.

What can Developer Tools do?
It exposes 2 tools, read directly from the server on our last check. Among them: fetch_workspace_docs, search_workspace_docs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Developer Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 283 ms. The bar chart above shows every period we have measured.
How do I connect Developer Tools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Developer Tools need an API key?
No. Developer Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Developer Tools?
It answers our handshake in 283 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.