DevSpeak
- juanjaragavi/devspeak
DevSpeak is an MCP server that translates technical text into formal specs from any AI IDE or agent.
About
DevSpeak MCP is the official Model Context Protocol bridge to DevSpeak, a service that turns informal technical language into formal specifications suitable for implementation planning. developers who brainstorm in natural language but need crisp PRDs, API contracts, or feature specs can invoke it during validate and early build documentation work so the same agent session moves from vague idea to structured scope. The server offers stdio via @devspeak/mcp 1.0.3 and a remote streamable-http endpoint at https://devspeak.dev/mcp, with a required DEVSPEAK_API_KEY from the DevSpeak dashboard. It complements planning skills by outsourcing spec formalization to a dedicated API rather than hoping the model improvises structure.
- Translates technical text into formal specifications
- Official DevSpeak MCP: stdio npm @devspeak/mcp and remote streamable-http
- Requires DEVSPEAK_API_KEY from DevSpeak dashboard
- Optional DEVSPEAK_API_URL override; default https://www.devspeak.dev
- Works from any AI IDE or agent supporting MCP
DevSpeak by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env DEVSPEAK_API_KEY=YOUR_DEVSPEAK_API_KEY --env DEVSPEAK_API_URL=YOUR_DEVSPEAK_API_URL devspeak -- npx -y @devspeak/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | @devspeak/mcp |
|---|---|
| Transport | STDIO, HTTP |
| Auth | Required |
| Repository | juanjaragavi/devspeak ↗ |
What it does
Turn messy technical notes and chat dumps into formal specs your agent can implement, via DevSpeak from any MCP IDE.
Who is it for?
Best when you think out loud in the IDE and want a consistent spec layer before writing code.
Skip if: Skip if you already enforce rigid in-repo spec templates only, or workflows with no DevSpeak account and no appetite for an external API.
What you get
After you add the server and API key, informal notes become formal DevSpeak specifications ready for plans, tickets, or codegen.
- Formal specifications derived from raw technical input
- MCP-accessible spec translation in the same session as planning
- Clearer handoff from validate scope to build implementation
By the numbers
- Package version 1.0.3
- Required env DEVSPEAK_API_KEY
- Remote MCP URL https://devspeak.dev/mcp (streamable-http)
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
External spec-formalization API via MCP, not an in-repo brainstorming skill or static PRD template.
FAQ
Who is DevSpeak for?
Developers using Claude Code, Cursor, or other MCP clients who want DevSpeak to structure technical text into formal specs.
When should I use DevSpeak?
Use it when scoping a feature, MVP, or integration after brainstorming and before detailed implementation.
How do I add DevSpeak to my agent?
Create a DEVSPEAK_API_KEY in DevSpeak Settings, then configure either stdio @devspeak/mcp or the remote https://devspeak.dev/mcp endpoint in your MCP client.