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

# Overview

> Overview of Ditto's MCP server for AI coding agents

## What is the Ditto MCP server?

The Ditto MCP (Model Context Protocol) server connects AI coding agents to your team's content in Ditto. It gives agents access to your style guide rules and existing text so they can write on-brand text, reuse existing strings, and manage your style guide when generating code.

With the MCP server, your AI coding agent can:

* **Follow your style guide rules** when writing UI text, so generated copy is consistent with your team's guidelines.
* **Search and reuse existing text** from Ditto projects, so agents reference approved text instead of generating new ones.
* **Manage style guide rules** — create, update, and delete rules and inspect workspace tags directly from your editor.

## How it works

The Ditto MCP server runs locally and exposes the following [tools](/mcp-reference/tools) to any MCP-compatible client:

1. **`get_styleguide_rules`** fetches your workspace and project-level style guide rules from Ditto.
2. **`search_ditto_text`** searches your Ditto projects for existing text items.
3. **`create_styleguide_rule`** adds a new rule to a workspace style guide.
4. **`update_styleguide_rule`** updates an existing style guide rule.
5. **`delete_styleguide_rule`** deletes a style guide rule.
6. **`get_workspace_tags`** lists the tags currently in use across the workspace.

Your AI agent calls these tools automatically based on the instructions you provide. For example, you can add a line to your `CLAUDE.md` or `.cursorrules` file telling the agent to check Ditto's style guides before writing any user-facing text. See [Example use cases](/mcp-reference/examples) for more.

## Project configuration

Add a `ditto/config.yml` or `ditto/config.yaml` file in your project root to scope MCP tool calls to specific Ditto projects:

```yaml theme={null}
projects:
  - id: "your-project-developer-id"
```

When present, the MCP server will automatically include these project IDs in tool calls, so results are scoped to the projects relevant to your codebase.