MCP server

Before you connect

The MCP server lets an outside AI client work in one Systemly workspace through Model Context Protocol. It is available on the Agency plan. Create an API key for the target workspace under Settings → Developer tools → API keys, then open the AI agents tab for the endpoint and client-specific setup snippets. The hosted endpoint is https://app.systemly.com.au/api/mcp.

Use a client that supports remote MCP over Streamable HTTP and can send theAuthorization: Bearer <key> header. The server is stateless: every request must carry the key, and there is no session ID to retain. The AI agents tab includes examples for Claude Code, Claude Desktop, and other compatible clients.

Connect and test an agent

1. Choose the workspace, create a clearly named API key, and store the full value securely.
2. Copy the endpoint and the configuration for your MCP client from Settings → Developer tools → AI agents.
3. Set the bearer header in that client, connect, and list the available tools.
4. Try a read-only task first, such as finding a contact or summarising open opportunities.

If a client only supports local-process MCP and cannot add a bearer header to a remote HTTP endpoint, it cannot connect directly using these instructions.

What an agent can do

An MCP key is bound to its workspace and its creator. The server rechecks that the creator still belongs to the organisation and can reach the workspace, then filters tools by their current role, per-member overrides, and the key's scopes. If the creator loses workspace access, their agent loses it too. An agent cannot use the key to read another client workspace.

Write tools are withheld when Let the assistant make changes is off underSettings → AI assistant, even though keys created in the UI currently have both read and write scopes. The available tool groups and the switch state appear on the AI agents tab. The tool set does not include record deletion or unapproved public publishing.

With write tools on, an agent can also make media: generate images, start a video render, and check on it until it finishes. Renders use the same key or AI usage as AI Studio, and the agent can switch the brand kit on with use_brand.

If the connection fails

• HTTP 401: check the bearer header and whether the key was revoked or replaced.
• HTTP 403: check the Agency plan, the key creator's current access, and whether the requested tool is allowed.
• HTTP 429: follow Retry-After; see Rate limits.
• Missing write tools: check the workspace AI actions switch and the key owner's permissions.