Configure the DevSpeak MCP Server

The DevSpeak MCP server gives compatible AI clients direct access to the DevSpeak production translation tools.

DevSpeak supports two MCP transports today:

Local stdio via the published npm package @devspeak/mcp

Hosted streamable-http via https://www.devspeak.dev/mcp

What the MCP server exposes

Once configured, users can access twelve tools:

translate_text

translate_markdown

refine_translation

optimize_text

summarize_input

get_history

get_account_info

detect_language

list_languages

auth_confirm

patch_translation_note

publish_linkedin_post — admin-only; previews by default and publishes only when dryRun is explicitly false

The server also exposes read-only resources for supported languages, API reference, and workflow reference.

These tools run through the live DevSpeak API, so users do not need a separate local backend.

Requirements

You will need:

A DevSpeak API key

Node.js for local stdio installs, or a remote-MCP-capable client for the hosted endpoint

An MCP-capable client such as Claude Code, Claude Desktop, Cursor, Gemini CLI, Antigravity, or a similar host

Recommended local setup: Claude Code

Add the server to ~/.claude/settings.json (user level) or .claude/settings.json (project level):

``json

{


  "mcpServers": {
    "devspeak": {
      "command": "npx",
      "args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
      "env": {
        "DEVSPEAK_API_KEY": "dsk_live_your_key_here"
      }
    }
  }
}

`Claude Desktop example`

Add the following entry to your Claude Desktop configuration file.

`json


{
  "mcpServers": {
    "devspeak": {
      "command": "npx",
      "args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
      "env": {
        "DEVSPEAK_API_KEY": "dsk_live_your_key_here"
      }
    }
  }
}

Typical config file locations:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%/Claude/claude_desktop_config.json

`Cursor example`

In Cursor, add a command-based MCP server with:

Command: npx

Arguments: -y -p @devspeak/mcp devspeak-mcp

Environment variable: DEVSPEAK_API_KEY=dsk_live_your_key_here

`Hosted endpoint for remote-capable clients`

If your MCP host supports streamable-http, point it to:

Endpoint: https://www.devspeak.dev/mcp

Auth header: x-api-key: dsk_live_your_key_here

Use the www host. The apex devspeak.dev answers with a 308 redirect, and several MCP clients do not follow redirects on streamable-http POSTs.

Clients that only support bearer-style auth can send Authorization: Bearer ; the server normalizes that header to x-api-key before auth checks.

Gemini CLI, Antigravity, and other remote-capable hosts should use whichever transport their MCP config model prefers: the local npm package for stdio, or the hosted endpoint above for remote sessions.

`Verify the connection`

After restarting the client, test the setup by asking the agent to run:

auth_confirm

list_languages

If the key is valid, the agent should confirm that it can reach the DevSpeak backend.

`Pairing MCP with DevSpeak skills`

The MCP server provides the tools. The public DevSpeak skills provide the workflow instructions. In practice, most users should install both:

`bash

npx skills add devspeak-dev/devspeak-skills

That combination gives the agent both runtime access and task-specific guidance.

`Public discovery surfaces`

Current public discovery points for the MCP server are:

Official MCP Registry: io.github.juanjaragavi/devspeak

mcp.so: https://mcp.so/server/devspeak

Smithery Connect: juanamillo-1duz/devspeak`