Configure the DevSpeak MCP Server

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

What the MCP server exposes

Once configured, users can access tools such as:

translate_text

translate_markdown

refine_translation

detect_language

list_languages

auth_confirm

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

Requirements

You will need:

Node.js

A DevSpeak API key

An MCP-capable client such as Claude Desktop or Cursor

Claude Desktop example

Add the following entry to your Claude Desktop configuration file.

``json

{


  "mcpServers": {
    "devspeak": {
      "command": "npx",
      "args": ["-y", "@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 @devspeak/mcp

Environment variable: DEVSPEAK_API_KEY=dsk_live_your_key_here

`Verify the connection`

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

auth_confirm

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.