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

# Docs MCP server

> Connect FinSync documentation to your AI assistant via Model Context Protocol (MCP) over HTTP.

# Docs MCP server

FinSync publishes a **Model Context Protocol (MCP)** endpoint so assistants and IDE integrations can search and read these docs programmatically—without scraping the site or copying snippets by hand.

**Endpoint:** [https://docs.finsync.ar/mcp](https://docs.finsync.ar/mcp)

The server advertises HTTP transport and is intended for clients that support remote MCP (for example, tools that let you register an MCP URL).

## What you get

| Tool                    | Purpose                                                                                                                                                          |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `search_fin_sync_api`   | Search the FinSync API knowledge base: guides, API references, examples, and implementation notes. Results include titles and paths you can open in this portal. |
| `get_page_fin_sync_api` | Fetch the **full** Markdown for a specific docs page when you already have its path (for example, from a search result).                                         |

Together, these tools let an assistant **discover** content with natural-language queries, then **pull** the complete page when depth matters.

## When to use it

* **Building agents or automations** that need accurate, up-to-date FinSync API behavior.
* **IDE copilots** that can call MCP tools while you implement integrations.
* **Support or internal workflows** where answers should be grounded in the same sources as this documentation.

For traditional browsing, you can still use this site, [`llms.txt`](https://docs.finsync.ar/llms.txt), and the OpenAPI-backed **API Reference** tab.

## Quick mental model

1. Call `search_fin_sync_api` with a question or keywords.
2. Use paths from the results (or that you already know) with `get_page_fin_sync_api` for full page content.
3. Cross-check critical details in the **API Reference** tab or your environment’s OpenAPI client.

## Configure in your client

This server uses **HTTPS** and **streamable HTTP** MCP (not a local `stdio` command). Use a client version that supports **remote / URL-based** MCP. After any config change, **fully quit and restart** the app so it reloads servers.

### Cursor

Cursor reads MCP from **`~/.cursor/mcp.json`** (all workspaces) or **`.cursor/mcp.json`** in a project (commit that file if the team should share the same tool).

Add an entry with the docs URL:

```json theme={null}
{
  "mcpServers": {
    "finsync-docs": {
      "url": "https://docs.finsync.ar/mcp"
    }
  }
}
```

Merge this with existing servers inside the same `"mcpServers"` object instead of replacing the whole file. See [Model Context Protocol (MCP) in Cursor](https://cursor.com/docs/context/mcp).

### Claude Code

**CLI (recommended):** from your project directory, add an HTTP transport server:

```bash theme={null}
claude mcp add --transport http finsync-docs https://docs.finsync.ar/mcp
```

Optional scopes (see [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp)):

* **`--scope project`** — writes to **`.mcp.json`** at the repo root (good for teams; review before committing).
* **`--scope user`** — available in all projects (stored in your user config).

If the endpoint ever requires a header (FinSync’s public docs MCP does not today), use:

```bash theme={null}
claude mcp add --transport http finsync-docs https://docs.finsync.ar/mcp \
  --header "Authorization: Bearer your-token"
```

**Check status:** run `claude mcp list` or use the `/mcp` command in a session.

**Project file example** (`.mcp.json` at the repository root), equivalent to a project-scoped HTTP server:

```json theme={null}
{
  "mcpServers": {
    "finsync-docs": {
      "type": "http",
      "url": "https://docs.finsync.ar/mcp"
    }
  }
}
```

### Claude Desktop

Config file location:

* **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
* **Linux:** `~/.config/Claude/claude_desktop_config.json`

Example entry (shape matches other Anthropic examples that use `type` + `url` for HTTP servers):

```json theme={null}
{
  "mcpServers": {
    "finsync-docs": {
      "type": "http",
      "url": "https://docs.finsync.ar/mcp"
    }
  }
}
```

Anthropic’s help center describes managing tools from the desktop app (extensions, connectors, developer logs). If an HTTP server does not appear after restart, confirm you are on the **latest Claude Desktop** and check **Settings → Connectors** / developer logs—capabilities differ by version. As an alternative, **Claude Code** (above) or **Cursor** are often simpler for URL-only MCP servers.

### Claude.ai (web)

If you use Claude in the browser and your plan supports it, add and manage connectors under **[claude.ai/settings/connectors](https://claude.ai/settings/connectors)**. When you use **Claude Code** while signed in with the same account, connectors configured there can show up alongside locally added servers; see [Use MCP servers from Claude.ai](https://code.claude.com/docs/en/mcp#use-mcp-servers-from-claude-ai) in the Claude Code docs.

## Troubleshooting

* **JSON must be valid** — a trailing comma or missing brace can prevent *all* MCP servers from loading.
* **Only `stdio` supported** — some older setups expect a `command` + `args`. This FinSync endpoint is **URL-only**; upgrade the client or use one that supports HTTP MCP.
* **Corporate proxies** — allow HTTPS access to `docs.finsync.ar` if tools fail to connect.

## Related

* [Overview — AI and LLM support](/docs/index#ai-and-llm-support)
* [Quickstart](/docs/quickstart)
* [Authentication](/docs/authentication)