Getting Started

Overview

This page walks through connecting an AI assistant to Matia over MCP, from prerequisites to your first successful call. MCP tool access follows your existing role.

Prerequisites

• A Matia account in the workspace you want to connect to.
• MCP access enabled for your workspace. If you're not sure whether it's turned on for your plan, contact Matia Support.

Claude (Desktop and claude.ai)

Matia is a registered Claude connector, so there's no server URL to find or paste. Just connect it from Claude's connector directory:

1. Open Settings → Connectors.
2. Search for Matia and click Connect.
3. Sign in with your Matia account and approve the connection.
4. Once approved, Matia's tools are available in your conversation.

Claude Code

Claude Code doesn't yet read from the connector directory, so add the server directly with its URL:

claude mcp add --transport http matia https://api.matia.io/mcp

Or, from inside a Claude Code session, run /mcp and follow the prompts to add a new server with that URL. The first time a Matia tool is called, Claude Code opens your browser for the same Matia sign-in and approval step.

Other AI assistants

Matia runs a standard remote MCP server, so any client that supports remote MCP servers over HTTP can connect to it. There's nothing to install locally and no API key to generate. You need somewhere in the client to paste a server URL, and the client must support OAuth.

Server URL

https://api.matia.io/mcp

Transport: Streamable HTTP. Matia doesn't publish a stdio or SSE endpoint, so clients that only support local stdio servers can't connect directly.

Authentication: OAuth. Your client discovers Matia's authorization server from the URL above, registers itself, and opens a browser for you to sign in and approve the connection. You won't be asked for a client ID, secret, or token.

Many clients take a JSON configuration block along these lines:

{
  "mcpServers": {
    "matia": {
      "type": "http",
      "url": "https://api.matia.io/mcp"
    }
  }
}

Field names vary between clients. type may be called transport, the value may be spelled streamable-http, and some clients nest servers differently or offer a form instead of a config file. Check your client's own MCP documentation for the exact shape; the URL and the transport are the only Matia-specific parts.

Once connected, the tools your assistant can see depend on your Matia permissions. See Authentication & Access Management. For things to try first, see Example Prompts.