Skip to content

developer-tools MCP server

goog.workspace-developer/developer-toolsworkspace-developer.googstreamable-httpv1.0.0Scanned

Provides tools for searching Google Workspace documentation and much more.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the developer-tools MCP server can do

The developer-tools MCP server is published by workspace-developer.goog, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (search_workspace_docs and fetch_workspace_docs); 2 tools bring in text other people can write (search_workspace_docs and fetch_workspace_docs); 1 tool can send data out of your system (fetch_workspace_docs). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • fetch_workspace_docsFetches the content of a Google Workspace documentation page such as those returned by the `search_workspace_docs` tool.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "fetch_workspace_docs" says "fetch": a word for reading.

    What it can reach

    • private-dataThe name "fetch_workspace_docs" says "fetch" and "doc": it reads documents.
    • private-dataThe description's first sentence says "fetch" and "doc": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetches the content of a Google Workspace documentation page such as those returned by the `search_workspace_docs` tool.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_workspace_docsSearches the latest official Google Workspace documentation, including API references, conceptual guides, tutorials, and code examples.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_workspace_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_workspace_docs" says "search" and "doc": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Searches the latest official Google Workspace documentation, including API references, conceptual guides, tutorials, and code examples.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__developer-tools__fetch_workspace_docs"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Posture changes

  1. Oct 29, 2026
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. tools/list served without credentials: no -> yes; Protocol version: none -> 2025-06-18.View diff
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http developer-tools https://workspace-developer.goog/mcp
claude mcp add --transport http developer-tools https://workspace-developer.goog/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__developer-tools__search_workspace_docs"
    ],
    "ask": [
      "mcp__developer-tools__fetch_workspace_docs"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as developer-tools. Review it before you use it.

Capability tags behind 2 rules
  • mcp__developer-tools__search_workspace_docs private-data, untrusted-input
  • mcp__developer-tools__fetch_workspace_docs private-data, untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/goog.workspace-developer/developer-tools/verify?hash=4c6b4ca8e7636405063e60af467b33353fcd751371f5e147b3c516d14bfb8f7f" | jq -e '.changed == false'

Pinned hash 4c6b4ca8e763, from Nov 15, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/goog.workspace-developer/developer-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for goog.workspace-developer/developer-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/goog.workspace-developer/developer-tools.svg)](https://radar.anlyon.com/servers/goog.workspace-developer/developer-tools)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

developer-tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the developer-tools MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the developer-tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the developer-tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the developer-tools MCP server have?

2 tools: 2 read. search_workspace_docs and fetch_workspace_docs.

Does the developer-tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the developer-tools MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fetch_workspace_docs.

Has the developer-tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.