Sourced MCP Server

Sourced MCP server exists for a simple reason — assistants are far more useful when they can act on Sourced directly instead of describing what you should do. Sourced.dev provides coding agents with direct access to dependency source code through the Model Context Protocol (MCP). Instead of relying on training data or web searches, agents can read, search, and.

What the assistant can call

Once Sourced is connected, these are the calls the assistant has available:

• PyPI — 800,000+ packages
• RubyGems — planned
• read — Read a file from a package's source code with line numbers
• grep — Search for a regex pattern across a package's source tree
• glob — Find files matching a glob pattern within a package

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sourced's toolset — PyPI, RubyGems, read and 2 more — is a fair guide to whether it matches your workflow. It is maintained by ryancodrai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sourced mcp server does with a few real requests.