> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jabrod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP servers

> Use Jabrod products from Claude, Cursor and more.

The Model Context Protocol (MCP) lets an AI app such as Claude Code, Claude Desktop or Cursor use another program's tools. Art Studio, Art Studio for Windows (JBD), Context and Evals have MCP servers today.

| Product | Server | Available | Setup |
| - | - | - | - |
| Art Studio for Windows (JBD) | `jbd-mcp.exe`, a local program installed with JBD | Yes | [Connect JBD](https://docs.jabrod.com/art/jbd/mcp.md) |
| Art Studio | `https://jabrod.com/api/mcp/art` | Yes | [Connect Art Studio](https://docs.jabrod.com/art/studio/mcp.md) |
| Signals | Remote server on jabrod.com | Not yet | [Signals MCP](https://docs.jabrod.com/signals/mcp.md) |
| Evals | `https://jabrod.com/api/mcp/evals` | Yes, on Evals Pro | [Connect Evals](https://docs.jabrod.com/evals/mcp.md) |
| Context | `https://jabrod.com/api/mcp/context` | Yes | [Connect Context](https://docs.jabrod.com/context/mcp.md) |

## Local and remote servers

* A **local** server is a program on your computer. The client starts it and talks to it over stdio. JBD's server is local because your projects are local.
* A **remote** server runs on jabrod.com and works on the data in your Jabrod account. The client connects to it over HTTPS and either [signs in with Jabrod](https://docs.jabrod.com/platform/sign-in.md#mcp-clients) or sends a personal API key from [jabrod.com/app/keys](https://jabrod.com/app/keys). Art Studio, Context and Evals have remote servers.

## Tool names

Clients show a tool with the server's name in front of it. If you add JBD's server as `jbd`, Claude Code shows `command_run` as `mcp__jbd__command_run`. Name each server after its product so the tools are easy to tell apart.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.