Start a conversation
Model Context Protocol

Put Kiberon Labs project data inside your agent workflows.

Connect supported AI clients to Kiberon Labs through MCP. Your agents can retrieve project updates, timelines, documents, and messages using a scoped API key or an OAuth 2 client.

Generate an API keyView configuration
Available now

Supported MCP servers

01 integration
Available

Kiberon Labs

Projects MCP

Bring your Kiberon Labs project data into your agent workflows. Connect with a scoped organization API key or a standard OAuth 2 client with dynamic client registration enabled.

Endpointhttps://clients.mcp.kiberonlabs.com/mcp
Least-privilege access by default

OAuth clients that register without write scopes default to read-only access. API keys and OAuth clients use the published Kiberon Labs scopes.

Project updates

Get the latest status and progress from your active Kiberon Labs projects.

Timelines

Check delivery milestones and upcoming work without leaving your agent.

Shared documents

Retrieve documents shared with your organization when you need more project context.

Team messages

Read organization messages, with sending available only when you grant the write scope.

API key configuration

Connect with an API key in four steps.

  1. 1

    Open your client portal

    Sign in with the account linked to your organization.

  2. 2

    Create an API key

    Choose the Read Only Client Portal preset, create the key, and copy it when shown.

  3. 3

    Add the remote MCP server

    Use the endpoint and pass your API key as a bearer token.

  4. 4

    Start asking for project context

    Your agent can now call the available tools within the scopes granted to the key.

mcp.json
{
  "mcpServers": {
    "kiberon-projects": {
      "type": "http",
      "url": "https://clients.mcp.kiberonlabs.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

This example uses an API key. OAuth 2 clients can connect to the same endpoint using dynamic client registration. Clients that do not request write scopes receive read-only access.

Client compatibility

Use the authentication flow your client supports.

The Projects MCP server supports scoped organization API keys and OAuth 2 clients with dynamic client registration. Due to limited client capabilities, resources are also exposed as tools so compatible clients can use every available capability.

  • Streamable HTTP endpoint
  • API key access control
  • OAuth 2 dynamic client registration
  • Tool-first compatibility
Scopes control access

Read access covers projects, documents, timelines, and messages. Grant write:messages only when the client needs to send messages.

Ready to connect?

Bring your Kiberon Labs projects into your agent.

Open the client portal