How is access controlled?

The endpoint is scoped to your API key. An agent only sees the tools and files on your account, and rotating the key revokes access immediately.

How does pricing work?

Connecting and browsing the catalog is free. Tool calls that do AI work draw on credits, the universal currency across all Developers Digest apps, with costs shown up front.

MCP

One MCP endpoint, progressively disclosed

Point any agent at a single URL and it reads a lean index first, a manifest on request, then the one file the task actually needs.

How it works

From zero to shipped in three steps

Step 1
Start with a lean index
On connect, the agent reads a small index of the tool groups available on your account. No thousand-line manifest dumped into the context window before the first turn.
Step 2
Expand to a manifest on demand
When a task touches a group, the agent requests that group's manifest and sees only those tools. Capability transport without the flat, context-hungry list MCP usually ships.
Step 3
Load the one file the task needs
Progressive disclosure runs all the way down: the agent pulls the single skill or resource file it needs, when it needs it, and nothing else.

Connect

One config, any client

Add the endpoint to your MCP client config and authenticate with your API key. The same block works in Claude Code, Cursor, or any MCP-aware client.

mcp.json

{
  "mcpServers": {
    "developers-digest": {
      "url": "https://www.developersdigest.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer dd_live_xxxxxxxxxxxxxxxx"
      }
    }
  }
}

What you get

Built for shipping, not fiddling

Your whole account, one endpoint

Skills, files, memory, and generation tools are all reachable through a single MCP URL. Register once and every client sees the same surface.

Progressive disclosure, not flat lists

MCP solved capability transport but ships flat tool lists. This endpoint layers index, manifest, and file so an agent pays context only for what the task needs.

A tool catalog that grows with you

Add a skill, connect a file source, or turn on a generation tool and it appears in the catalog automatically. The manifest is always current.

Connect from any client

Claude Code, Cursor, or any MCP-aware client connects with one URL and your API key. No per-client setup and no SDK to wire up.

Scoped to your key

The endpoint is scoped to your API key, so an agent only ever sees the tools and files on your account. Rotate the key to cut access instantly.

Credits that travel

MCP tool calls run on the universal Developers Digest credit balance. The same credits power chat, memory, skills, and every other app in the suite.

Questions

Common questions

All 6 FAQs

What is the MCP platform?

It is a single Model Context Protocol endpoint that exposes your Developers Digest account (skills, files, memory, and generation tools) to any MCP client, using progressive disclosure so agents load only what a task needs.

What is progressive disclosure here?

Rather than dumping a flat tool list into the context window, the endpoint serves a lean index first, a group manifest when the agent asks, and the single file it needs at the moment of use. Agents pay context only for the task in front of them.

Which clients can connect?

Any MCP-aware client. Claude Code, Cursor, and other MCP clients connect with one endpoint URL and your API key, with no per-client SDK setup.

What tools are exposed?

Your skills, files, memory, and generation tools, all through the same endpoint. As you add capabilities to your account, they appear in the catalog automatically.

Read

From the blog

All posts

One MCP endpoint, progressively disclosed

From zero to shipped in three steps

Start with a lean index

Expand to a manifest on demand

Load the one file the task needs