Creytix
Sign in
ReferencePreview

Creytix Connect MCP

Native MCP registry — host your own tool connections instead of a third-party gateway.

AI

Preview — early access.

Overview

Creytix Connect MCP exposes the tools already live in your Connect registry — Mail, SEO OS, Scheduling, and the rest — as MCP tools an AI agent can call directly. It's a self-hosted registry, not a metered, per-call SaaS layer sitting between your agent and your tools.

How it works

Your workspace's Connect registry is the source of truth for which tools exist and what they do. Connect MCP takes that same registry and makes it available in the Model Context Protocol shape:

  1. Your workspace's native tools are listed in the registry.
  2. Connect MCP generates an MCP configuration referencing those tools for your workspace.
  3. You add that configuration to an MCP-compatible agent, which can then call the tools you've approved.

Steps

  1. •

    Open the MCP section under Connect

    From Connect in the Creytix Control Panel, find the MCP configuration for your workspace.

  2. •

    Copy your workspace's MCP config

    Copy the generated configuration, which lists the native tools available to your workspace.

  3. •

    Add it to your agent

    Paste the configuration into the MCP settings of the agent or client you use — anything that speaks MCP.

  4. •

    Approve tool calls as they happen

    When your agent calls a Connect tool, review and approve the call the same way you would any other tool use.

Capabilities

  • Self-hosted registry — the tool list comes from your own Connect registry, not a third-party SaaS broker.
  • No usage-based meter — Connect MCP doesn't add a per-call billing layer on top of tools you already run.
  • Built on tools you already know — every tool exposed through MCP is one you can also read about in the Connect docs.
  • Works with MCP-compatible agents — not locked to a single vendor's agent product.

Limits & honest scope

Connect MCP is in preview — early access, and there's a real gap between what exists today and the full vision.

  • The current configuration experience is a copy-to-clipboard stub, not a packaged, installable client yet.
  • Only a subset of Connect tools is exposed through MCP today — check your workspace's config for what's actually available before building a workflow around a specific tool.
  • Fine-grained, per-tool permission scoping isn't built yet — treat every exposed tool as something you should review before approving, not something pre-scoped to be safe by default.
  • This is not a hosted, third-party MCP marketplace — there's no cross-customer tool catalog, just your own workspace's registry.

Related