Cinode

Cung cấp cho các tác nhân cái nhìn tổng quan về con người, dự án, kỹ năng và nhiệm vụ.

Xem trên cinode.com

Tài liệu

The Cinode MCP (Model Context Protocol) server securely connects AI clients and MCP-compatible agents to your Cinode environment so they can access your organisation’s live data. That gives agents the same contextual view of people, projects, skills and assignments that your team has, instantly, so they can assist, analyse, update and automate with confidence.

Think of it as giving your AI assistant a working knowledge of your Cinode setup, without exposing data you don’t want shared.

Why use the Cinode MCP Server?

  • Smarter AI support – Agents act with real context from your Cinode data
  • Faster workflows – Reduce time spent on manual updates and lookups
  • Always in sync – Agents work with live, up-to-date information
  • Secure by design – Fine‑grained access control over what agents can see and change

Getting Started

You can access our MCP server with Streamable HTTP at https://mcp.cinode.com/_mcp

You need to be on a paid plan using Cinode to have access to our API and our MCP Server.

Authentication Methods

Our MCP server supports two authentication approaches:

  1. OAuth (recommended): Browser-based sign-in using Dynamic Client Registration (DCR). No manual token handling.
  2. Bearer Token: Static API token authentication
  3. Basic Credentials: Client ID and Client Secret authentication

Bearer tokens and Basic credentials are sensitive information.

Never share or store them insecurely (for example: in screenshots, public/shared documents, ticket attachments, chat tools like Teams/Slack, emails, sticky notes, or websites). Always use secure storage and only transmit credentials over encrypted connections (HTTPS/TLS).

How OAuth (DCR) works

With OAuth you don't create or paste any token. Supported MCP clients connect to the server URL and handle authentication for you:

  1. Point the client at https://mcp.cinode.com/_mcp and choose OAuth (or simply connect, if the client auto-detects it).
  2. The client registers itself automatically with Cinode using Dynamic Client Registration (RFC 7591) and starts an OAuth 2.1 authorisation flow.
  3. A browser window opens asking you to sign in to Cinode and approve access.
  4. Once approved, the client receives an access token and connects. Access is scoped to your own Cinode roles and permissions, exactly as with the other methods.

How Basic Credentials work

Basic authentication uses your Client ID and Client Secret:

  1. Join them with a colon: CLIENT_ID:CLIENT_SECRET
  2. Base64-encode the full string.
  3. Send it in the Authorization header: Authorization: Basic BASE64_ENCODED_VALUE

When you generate a Personal API Account in Cinode we'll show you an encoded and ready-to-use string which you immediately can use within the Authorization header. Read more here.

Configuration Examples

The examples below are generic templates. Always refer to your provider's official documentation for the most up-to-date configuration instructions, as setup details may vary between versions and providers.

For Bearer token authentication:

{
"mcpServers": {
"cinode": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.cinode.com/_mcp",
"--header",
"Authorization: ${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_CINODE_API_TOKEN"
}
}
}
}

Note: Replace "npx" above with "C:\\Progra~1\\nodejs\\npx.cmd" if you're running Windows.

LLM Provider Setup Guides

  • Claude Desktop: MCP setup documentation or follow steps below:
    • Settings > Connectors > Add custom connector, pointing at https://mcp.cinode.com/_mcp
    • You only need to fill in Name and Server URL.
  • ChatGPT: Developer mode documentation or follow steps below:
    • Custom MCP connectors require Developer mode, available on Plus, Pro, Business, Enterprise and Edu accounts on the web.
    • Enable it under Settings > Apps > Advanced settings > Developer mode. On Business, Enterprise and Edu, a workspace admin must allow Developer mode first.
    • In Settings > Apps, click Create app, give it a name and paste the Server URL https://mcp.cinode.com/_mcp then select OAuth. Sign in to Cinode in the popup to authorise.
    • Open the app to toggle on the tools you want, then in a chat pick Developer mode from the + menu and select the Cinode app to use it.
  • Microsoft Copilot: MCP setup documentation (we've detailed the setup step-by-step here)
  • Claude Code: claude mcp add --transport http cinode https://mcp.cinode.com/_mcp
  • Cursor: Add to Cursor
  • VS Code: Add to VS Code

Security & Governance

Using MCP together with AI makes it possible to perform large-scale and automated changes to your Cinode data. While powerful, this also increases the risk of unintended or irreversible outcomes if prompts are incorrect or poorly tested.

When write access is enabled, AI-driven actions can modify or delete large amounts of data in a short time.

You are responsible for how MCP and AI tools are used in your organisation.
Changes made through MCP may be permanent and cannot always be undone.
Use MCP write capabilities at your own risk.

To reduce risk, Cinode strongly recommends that you:

  • Only enable write tools when necessary and when you are confident in both the technology and your prompt capabilities.
  • Validate prompts using read-only access before allowing create, update, or delete operations.
  • Limit write access to experienced users who understand Cinode’s data model and business impact.
  • Review and monitor automated workflows regularly.
  • Make sure your provider's privacy settings are set according to internal policy.

Data sharing & privacy

The Cinode MCP server does not send your data anywhere on its own. It only responds to the specific requests made by the AI client you connect - and only within the permissions of the account that authenticated.

What is shared, and with whom

  • When you connect an AI client (for example Claude/Anthropic, ChatGPT/OpenAI, or Microsoft Copilot), that client - not Cinode - is the party that processes your prompts and the data it retrieves.
  • Only the data an agent actually queries is returned to it and passed to your chosen AI provider. There is no bulk export or background syncing of your Cinode database.
  • Every request is scoped to the connected user's existing Cinode roles and permissions. An agent can never see or change more than that user already can.

Your responsibilities

  • How the retrieved data is stored, retained, or used for model training is governed by your chosen AI provider's terms and privacy settings, not by Cinode. Review and configure them according to your internal policy.
  • Any data processing agreement (DPA) for AI processing is between your organisation and the AI provider - not with Cinode.
  • Only enable write tools once you are confident in your prompts and permissions (see Security & Governance above).

Access and User Permissions

By default, employees can create personal API accounts and use those credentials (for example, Basic tokens) to connect MCP clients and AI tools to Cinode. This means that MCP access does not have to be centrally provisioned by an administrator.

This is not a security risk in itself:

  • A personal API account cannot be used to do more than the user can already do in the Cinode application.
  • All actions performed through MCP are limited by the user’s existing roles and permissions.
  • MCP access follows the same permission boundaries as normal interactive use of Cinode.

For organisations that want tighter control, administrators can:

  • Disable personal API account creation, preventing users from connecting MCP clients on their own.
  • Revoke or rotate existing API tokens at any time.
  • Adjust user roles and permissions, which immediately affects what MCP-connected tools can access or change.

This allows administrators to decide whether MCP access should be user-driven or centrally controlled, while maintaining full alignment with Cinode’s permission model.

Troubleshooting

  • Rate limiting: Cinode API limits apply. Reduce request frequency or contact Cinode Support for available packages for increased API limits

cinode.mcpb