Skip to main content
Glama
jambonz

@jambonz/mcp-schema-server

Official
by jambonz
README.md
# @jambonz/mcp-schema-server

MCP server that provides jambonz verb schemas and documentation to AI agents via the [Model Context Protocol](https://modelcontextprotocol.io/).

## How It Works

This server exposes the schemas and developer guide from the [@jambonz/schema](https://github.com/jambonz/schema) package as MCP tools. AI coding agents can query verb definitions, component types, callback payloads, and the full developer guide without needing local access to the schema files.

## Tools

| Tool | Description |
|------|-------------|
| `jambonz_developer_toolkit` | Returns the full developer guide and schema index. Call this first before writing any jambonz code. |
| `get_jambonz_schema` | Fetch the JSON Schema for any verb, component, or callback (e.g. `verb:say`, `component:synthesizer`, `callback:gather`, `guide:session-commands`). |

## Usage

### stdio transport

```bash
npx @jambonz/mcp-schema-server
```

### HTTP transport

```bash
npx @jambonz/mcp-schema-server --http --port 3000
```

## Configuration

### Claude Code CLI

Add to `.mcp.json` in your project root:

```json
{
  "mcpServers": {
    "jambonz": {
      "command": "npx",
      "args": ["-y", "@jambonz/mcp-schema-server"]
    }
  }
}
```

### Cursor

Add to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "jambonz": {
      "command": "npx",
      "args": ["-y", "@jambonz/mcp-schema-server"]
    }
  }
}
```

### VS Code

Add to `.vscode/mcp.json`:

```json
{
  "servers": {
    "jambonz": {
      "command": "npx",
      "args": ["-y", "@jambonz/mcp-schema-server"]
    }
  }
}
```

### Remote Hosted Server

A hosted instance is available at:

```
https://mcp-server.jambonz.app/mcp
```

To use the remote server in `.mcp.json`:

```json
{
  "mcpServers": {
    "jambonz": {
      "type": "url",
      "url": "https://mcp-server.jambonz.app/mcp"
    }
  }
}
```

## Development

### Local Testing

```bash
npm install
npm run build
node dist/index.js              # stdio transport
node dist/index.js --http       # HTTP on port 3000
```

### Release Process

Publishing is handled by GitHub Actions on `v*` tags. To release:

```bash
# After updating dependencies in package.json
npm install
git add -A && git commit -m "chore: update dependencies"

# Bump version and create tag
npm version patch   # or minor/major

# Push commit and tag to trigger publish workflow
git push origin main --tags
```

## Links

- [@jambonz/schema](https://github.com/jambonz/schema) -- schema package this server exposes
- [jambonz.org](https://jambonz.org) -- platform documentation
- [GitHub](https://github.com/jambonz/mcp-server)

## License

MIT

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: schema retrieval, example code, developer guide, and tool listing. No overlap in functionality.

Naming Consistency3/5

Mix of 'get_' prefix for two tools, 'list_' for one, and a noun-phrase name for 'jambonz_developer_toolkit'. Not fully consistent but still readable.

Tool Count4/5

4 tools is appropriate for the server's focused purpose of providing jambonz schema, examples, and developer resources. Not too few or too many.

Completeness4/5

Covers key developer needs: schema access, examples, developer guide, and pre-built tool listing. No major gaps for its scope.

Maintenance

ActivitySlowing
ResponsivenessNo issues