Developer · Local MCP server
Toolc
Optimizing compiler for agent tools: many MCP servers or REST APIs in, one lean endpoint out.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.toolc/toolc- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- dev.toolc
- Namespace
- Namespace verified by the MCP Registry via the domain toolc.dev · how
- Website
- toolc.dev
- Repository
- github.com/toolc-dev/toolc
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @toolc/cli | 0.1.1 | stdio |
How to connect Toolc
Toolc runs locally from a Node.js package published to the npm registry: @toolc/cli version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @toolc/cli@0.1.1. It reads the environment variable ANTHROPIC_API_KEY (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"toolc": {
"command": "npx",
"args": [
"-y",
"@toolc/cli@0.1.1"
],
"env": {
"ANTHROPIC_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Tokonomix CouncilMulti-model consensus: 2-6 frontier LLMs answer, an independent judge synthesises one answer. | Local · stdio |
| Tomorrow Central: Cloud Cost SentinelAWS pricing and cost estimates with no signup, plus read-only idle-resource scans of your account. | Remote · HTTPLive check: ✓ handshake |
| ToolarsLocal-first dev utilities: hash, base64, JWT, UUID, cron, URL codec. No network or telemetry. | Local · stdio |
| ToolbeltA collaborative substrate over your data: vector, knowledge graph, SQL, geospatial, streaming. | Remote · HTTPLive check: sign-in required |
| ToolforteExact IBAN, VAT, cron, regex answers; HTML/URL to hosted PDF or screenshot; agent memory; workflows. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ToolgovernWraps the toolgovern CLI as a single generic MCP tool for agent-tool policy validation. | Local · stdio |
| ToolmeshSelf-hosted MCP gateway. Turn any REST API into MCP tools via YAML (DADL). Authz, audit, policies. | Remote · HTTP |
| ToolPipe MCP Server238+ dev tools via MCP: JSON, QR, PDF, DNS, hash, UUID, code review, JWT, SSL, WHOIS, and more. | Remote · HTTPLive check: ✗ no handshake |