@spec2tools/stdio-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@spec2tools/stdio-mcplist all users"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Spec2Tools
Dynamically convert OpenAPI specs into AI agent tools at runtime—no code generation required.
Packages
This monorepo contains four packages:
Package | Description | Install |
Core utilities for OpenAPI parsing and authentication |
| |
Create AI SDK tools from OpenAPI specifications |
| |
CLI for interacting with OpenAPI-based AI tools |
| |
MCP server exposing OpenAPI endpoints as tools via stdio |
|
Related MCP server: OpenAPI to MCP Server
Quick Start
Using the SDK
import { createTools } from '@spec2tools/sdk';
import { generateText, stepCountIs } from 'ai';
import { openai } from '@ai-sdk/openai';
const tools = await createTools({ spec: './openapi.yaml' });
const result = await generateText({
model: openai('gpt-4o'),
tools,
prompt: 'List all users',
stopWhen: stepCountIs(3)
});
console.log(result.text);Using the CLI
# Set your OpenAI API key
export OPENAI_API_KEY=your-api-key
# Start the agent with an OpenAPI spec
npx @spec2tools/cli start --spec https://api.example.com/openapi.jsonUsing as MCP Server
# Add to Claude Code (or any MCP client)
claude mcp add --transport stdio my-api \
-- npx @spec2tools/stdio-mcp ./path/to/openapi.yamlCode Mode
Collapse all API endpoints into just 2 tools (search + execute), cutting input token usage by ~99.9%:
# MCP server with code mode
claude mcp add --transport stdio my-api \
-- npx @spec2tools/stdio-mcp ./openapi.yaml --code-mode// SDK with code mode
const tools = await createTools({
spec: './openapi.yaml',
codeMode: true,
});You can also convert any existing AI SDK tools to code mode:
import { toCodeModeTools } from '@spec2tools/core';
const codeModeTools = toCodeModeTools(existingTools);Thesis
You have a server. You have an OpenAPI spec. Now, with all the MCP hype, you're told you need to build another server—an MCP server—just so AI agents can call your API. You look it up: define tools, maintain handlers, keep it in sync with your actual API. But wait... you already described your API in OpenAPI. Why do we need to describe it to the agent twice?
Spec2Tools is the alternative. It reads your OpenAPI spec and exposes endpoints as tools—no code generation, no maintenance burden. Use it directly with the AI SDK, or spin up an MCP server instantly from your existing spec.
Development
# Clone the repo
git clone https://github.com/CahidArda/spec2tools.git
cd spec2tools
# Install dependencies
pnpm install
# Build all packages
pnpm buildLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CahidArda/spec2tools'
If you have feedback or need assistance with the MCP directory API, please join our Discord server