MCP servers

What MCP is

Model Context Protocol — Anthropic's open standard for AI agents to discover and call external tools. Niyra supports MCP natively, so any MCP-compatible server can plug in.

When to use a custom MCP

- Internal company API (CRM, database, deployment tool)
- Third-party service we don't have a Composio integration for
- Personal scripts you want Niyra to run
- Niche workflows specific to your business

How to add one

In chat

> "Add MCP server at https://my-internal-api.example.com/mcp"

Niyra walks you through:
1. Validates the server endpoint
2. Handles OAuth if required
3. Discovers available tools
4. Adds them to her runtime — no restart needed

In settings

Settings → Connections → MCP Servers → Add.

Provide:
- Server URL (HTTP) OR subprocess command (for local MCP servers)
- Auth type: none / API key / OAuth
- Friendly name (e.g., "Acme CRM")

Server requirements

Niyra is MCP spec-compliant. Your server must:

- Expose the MCP protocol over HTTP or stdio
- Support tool discovery via tools/list
- Accept tools/call with JSON arguments
- Return structured results

Anthropic's MCP spec is the canonical reference.

OAuth-secured MCP

For servers requiring OAuth:

1. Niyra detects the auth requirement
2. Redirects you to the server's authorization URL
3. Stores the token (encrypted) and refreshes proactively

Same security model as Composio integrations.

Examples of useful MCP servers

- Sentry — Read your team's recent errors
- PagerDuty — Acknowledge incidents from chat
- Internal CRM — Custom company tool
- Tableau / Looker — Query dashboards
- GitHub Actions — Trigger custom workflows

Removing a server

Settings → Connections → MCP Servers → Disconnect. Niyra immediately drops the tools from her runtime.

Limits

- Pro and Alpha can add up to 10 custom MCP servers
- HTTP servers must respond within 30s per call
- Stdio servers are sandboxed (no internet, limited filesystem)