mattt/emcee

emcee is a tool that provides a [Model Context Protocol (MCP)][mcp] server
for any web application with an [OpenAPI][openapi] specification.
You can use emcee to connect [Claude Desktop][claude] and [other apps][mcp-clients]
to external tools and data services,
similar to [ChatGPT plugins][chatgpt-plugins].
## Quickstart
If you're on macOS and have [Homebrew][homebrew] installed,
you can get up-and-running quickly.
bash
# Install emcee
brew install mattt/tap/emcee
Make sure you have Claude Desktop installed.
To configure Claude Desktop for use with emcee:
1. Open Claude Desktop Settings ( ⌘ , )
2. Select the "Developer" section in the sidebar
3. Click "Edit Config" to open the configuration file
The configuration file should be located in the Application Support directory.
You can also open it directly in VSCode using:
console
code ~/Library/Application\ Support/Claude/claudedesktopconfig.json
Add the following configuration to add the weather.gov MCP server:
json
"mcpServers": {
"weather": {
"command": "emcee",
"args": ["https://api.weather.gov/openapi.json"]
After saving the file, quit and re-open Claude.
You should now see 🔨57 in the bottom right corner of your chat box.
Click on that to see a list of all the tools made available to Claude through MCP.
Start a new chat and ask it about the weather where you are.
> What's the weather in Portland, OR?
Claude will consult the tools made available to it through MCP
and request to use one if deemed to be suitable for answering your question.
You can review this request and either approve or deny it.
If you allow, Claude will communicate with the MCP
and use the result to inform its response.
## Why use emcee?
MCP provides a standardized way to connect AI models to tools and data sources.
It's still early days, but there are already a variety of [available servers][mcp-servers]
for connecting to browsers, developer tools, and other systems.
We think emcee is a convenient way to connect to services
that don't have an existing MCP server implementation —
especially for services you're building yourself.
Got a web app with an OpenAPI spec?
You might be surprised how far you can get
without a dashboard or client library.
## Installation
### Installer Script
Use the [installer script][installer] to download and install a
[pre-built release][releases] of emcee for your platform
(Linux x86-64/i386/arm64 and macOS Intel/Apple Silicon).
console
# fish
sh (curl -fsSL https://get.emcee.sh | psub)
# bash, zsh
sh
> [!IMPORTANT]
> emcee doesn't use auth credentials when downloading
> OpenAPI specifications from URLs provided as command arguments.
> If your OpenAPI specification requires authentication to access,
> first download it to a local file using your preferred HTTP client,
> then provide the local file path to emcee.
### Transforming OpenAPI Specifications
You can transform OpenAPI specifications before passing them to emcee using standard Unix utilities. This is useful for:
Selecting specific endpoints to expose as tools
with [jq][jq] or [yq][yq]
Modifying descriptions or parameters
with [OpenAPI Overlays][openapi-overlays]
Combining multiple specifications
with [Redocly][redocly-cli]
For example,