# MCP Server

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

Sydekyks includes a built-in MCP (https://modelcontextprotocol.io/) server that lets AI assistants build missions, manage tables, test missions, and more - all through natural language.

## ​
Quick Start

### ​1. Get your server URL

- Select MCP in the application sidebar.

- Open the Connect tab.

- Choose Copy link to copy the URL shown by your deployment.

Use the displayed URL rather than constructing one yourself. The current interface uses a platform endpoint; an older build or deployment may expose a different route.

### ​2. Connect your client

Choose your client on the Connect tab for its setup instructions. The current interface includes Claude Code, Cursor and Claude, with additional clients under See all clients. Client support and button labels can change with the build.

Add the copied URL to the client’s MCP configuration or connector form. For a client that accepts JSON configuration, the structure is:

```
{
  "mcpServers": {
    "sydekyks": {
      "url": "PASTE_THE_URL_FROM_MCP_CONNECT"
    }
  }
}

```

Complete the authentication requested by your client. Confirm the deployment address and access being requested before authorizing the connection. Use the Connected Accounts tab to inspect connected clients.

### ​3. Start Building

Once connected, ask your AI assistant things like:

- “Create a mission that sends a Slack message when a new row is added to Google Sheets”

- “Check my mission for any issues before publishing”

- “Create a Contacts table and add 3 records”

- “Show me the last failed run and what went wrong”

- “What Slack triggers are available?”

## ​Tool Categories

Tools are organized into categories. Discovery tools are always available. Other categories can be enabled or disabled for the scope shown in the MCP Tools tab.

 | Category | Description

 | Discovery | Read-only tools for exploring flows, pieces, connections, tables, runs, and validation - including semantic search over the action and trigger catalog

 | Flow Management | Create, duplicate, rename, publish, and enable/disable flows

 | Flow Building | Add, update, and delete steps and triggers

 | Router & Branching | Add, update, and delete conditional branches

 | Annotations | Manage canvas notes

 | Tables | Full CRUD for tables, fields, and records

 | Testing & Runs | Test flows, inspect results, retry failures

See the Tools Reference (https://docs.sydekyks.com/mcp/tools) for the complete catalog with input schemas, and Tool Search (https://docs.sydekyks.com/features/availability) for how agents find the right action or trigger by describing a task in plain language.

## ​Self-Hosting Behind a Reverse Proxy

The MCP server and its OAuth endpoints are reachable both at the host root (https://your-instance.com/mcp) and under a path prefix (https://your-instance.com/<prefix>/mcp) when your reverse proxy routes https://host/<prefix>/* to Sydekyks.

For a subpath deployment to work, set AP_FRONTEND_URL to the full public URL including the prefix (e.g. https://your-instance.com/sydekyks). Sydekyks then advertises its OAuth issuer, authorization/token endpoints, protected-resource metadata, and the WWW-Authenticate discovery header under that prefix, so the entire handshake stays inside your proxy rule.

Clients that ignore the WWW-Authenticate header and probe the RFC well-known paths at the host root (https://host/.well-known/oauth-*) require an additional proxy rule forwarding those host-root paths to Sydekyks - that namespace is anchored to the host root by RFC 8414/9728 and cannot be relocated under the prefix. Header-honoring clients (such as Claude) do not need this.

## ​Security

- OAuth authentication - secure, token-based authentication handled automatically by your MCP client

- Stored connection credentials - credential values are kept outside normal connection metadata. This does not imply universal secret detection or redaction in every tool result.

- Authorized scope - tool access follows the authenticated scope. Platform connections can reach more than one authorized Command Center; confirm the scope shown by your client and deployment.

- Sensitive setup - ap_setup_guide returns instructions for the user to configure connections in the UI, rather than handling secrets through MCP

Tool results can contain permitted business data, mission inputs, step outputs and error details. A mission that returns or logs a sensitive value can expose it through run inspection. Use synthetic data for testing, limit authorized client access, and review what each tool sends to the external client.

## ​Product identity

The MCP server identifies as Sydekyks. Assistants receive the Command Center, Mission, Gadget and Connected Account vocabulary. Technical ap_* tools and integration package identifiers remain unchanged for compatibility. After upgrading, refresh or reconnect the MCP connection and start a new chat if an existing client still uses the old brand.