Latest Post - Release Notes 2026.3.13.0 Open the latest release notes
Creovia Tools Creovia Tools
Creovia Tools MCP

Connect Creovia Tools to your AI client.

Use one secure, standards-based connection to bring your Creovia identity into compatible AI workflows. No API key to copy. No separate account to manage.

Connect your client How access works
Connect

Give your AI the connection details.

Copy the prompt and let your AI add the server in the format its client expects, or use the common JSON configuration directly.

Ask your AI to connect it

Copy and paste this prompt

Add Creovia Tools as a remote MCP server.

Server name: creovia-tools
Server URL: https://creovia.tools/mcp

Use the supported remote MCP configuration and preserve any existing MCP servers or settings. Then start the OAuth authorization flow and open the sign-in page so I can sign in to Creovia Tools and approve access. Authentication uses OAuth, so do not create or request an API key.

After authorization, verify that the server is connected and its tools are available. If you cannot complete a step automatically, tell me the exact action I need to take and include any error message.

Add it to an MCP client

Common configuration shape

JSON 
{
  "mcpServers": {
    "creovia-tools": {
      "url": "https://creovia.tools/mcp"
    }
  }
}

Configuration keys can vary by client. If this shape is not accepted, use the prompt and let the client adapt it.

What happens next

One URL. Your account. Your approval.

  1. 01

    Add the server URL

    Open your client’s connector or MCP settings and add https://creovia.tools/mcp.

  2. 02

    Sign in to Creovia

    Your browser opens the normal Creovia Tools sign-in. The MCP client never receives your password.

  3. 03

    Review and approve

    Creovia shows the client name and requested permission before access is granted. Nothing connects silently.

Available today

Start with verified identity.

The first MCP tool is intentionally focused. It lets your client confirm which Creovia Tools account approved the connection before broader workflow permissions arrive.

whoami profile:read

Returns the signed-in user’s Creovia profile.

Access you can see

Built around explicit permission.

  • No pasted API keys. Secure browser sign-in replaces copied long-lived credentials.
  • Scoped access. Clients request named permissions for each capability.
  • Short-lived access. Access expires and refresh credentials rotate after use.
Good to know

MCP connection questions.

Ready when your client is.

Your client handles discovery and opens Creovia Tools when it is time to sign in.