Server MCP Clincoo: Kelola Proyek dari AI Eksternal

The Clincoo MCP Server turns every Clincoo project into a Model Context Protocol (MCP) server. That means your favorite external AI apps — Claude Desktop, Cursor, Windsurf, or any modern MCP client — can read and work on that project workspace directly: browsing files, writing code, fixing bugs, even publishing the site, all within the permissions you set. Every change syncs back to the Clincoo workspace in real time, with no manual export or import.

This article is the complete guide to the MCP Server feature: how to access it, the available permissions, the tools exposed to AI, how to plug the token into your client, and its advantages and benefits.

Feature summary at a glance

What MCP is and how it works

MCP (Model Context Protocol) is an open protocol that connects AI applications to data sources and working tools. Clincoo acts as the server provider: your project exposes a set of tools — reading files, writing files, deploying, and so on — and the external AI app you connect becomes a "client" allowed to call those tools.

The flow is simple: enable the MCP Server in the project settings, copy the endpoint and access token, paste them into your AI app’s MCP settings, and from then on the external AI can work on your Clincoo project within the permissions you enabled. You stay in full control: permissions can be changed anytime, the token can be regenerated, and all access can be revoked in one click.

How to enable the MCP Server

1. Make sure your account is on the Bisnis plan — MCP Server management is available on Bisnis.
2. Open the project you want to connect, then go to Settings → MCP Server.
3. Tap Enable MCP Server. Clincoo creates an endpoint and an access token dedicated to this project.
4. Set the permissions you need under Access Configuration, copy the endpoint and token, then paste them into your external AI app.
5. Watch what the AI does in the Recent Activity panel and adjust permissions anytime you need.

Connecting an external AI app

The MCP Server page provides three ready-to-use formats: the MCP Endpoint, the Access Token, and a combined URL + Token for apps that only offer a single URL field. For Claude, Cursor, or Windsurf, paste the following configuration block into the MCP settings (for example the mcp.json file):

{
  "mcpServers": {
    "clincoo": {
      "url": "https://app.clincoo.buzz/mcp?project=YOUR-PROJECT-ID",
      "headers": { "Authorization": "Bearer YOUR-ACCESS-TOKEN" }
    }
  }
}

Clients that do not support remote servers yet can use the mcp-remote wrapper — a short guide sits right below the configuration block on the MCP Server page. Never share your access token; anyone holding it can use every permission you enabled.

Access permissions: 10 switches you control

Each permission can be turned on and off individually, and changes save automatically. Only the read permission is on by default — everything else stays off until you enable it.

Tools available to AI

Each permission activates specific tools. Tools whose permission is off appear as disabled and cannot be called. Here is the complete list:

Token management and security

• Show/hide the token — the token is masked by default; tap the eye icon to reveal it.
• Regenerate the token — the old token stops working immediately; paste the new one into your AI clients.
• Revoke all access — permanently cancels the token. Every external AI connection to this project stops instantly.
• Recent Activity — this panel logs the latest operations performed by the external AI, with an option to clear the history.
• Least privilege principle — enable only the permissions you actually need. Read-only permission is enough for an AI that just reviews code.

If your plan drops below Bisnis, servers that are already connected keep running normally — only the management page locks until you upgrade again.

Advantages and benefits

• Work from your favorite AI editor without losing context — Cursor, Windsurf, or Claude reads your Clincoo project directly, with no back-and-forth file copying.
• Real-time synchronization — every file the external AI changes appears instantly in the Clincoo workspace and live preview.
• Granular per-operation permissions — you choose exactly what the AI may and may not do, per project.
• Transparent activity log — every external AI action is recorded, so you always know what happened to your project.
• No chat quota drain — the Clincoo AI Chat permission runs on a dedicated channel separate from your plan conversation quota.
• One source of truth — the Clincoo workspace stays the main workplace; the Clincoo AI assistant and external AI work on the same files.

Want a gentler first step? Start with read-only permission, watch the activity panel, then enable advanced permissions once you are confident. If anything goes wrong, check the Help Center or regenerate the token and reconnect your client.