The BlueConic MCP Client is a client-side tool that exposes all BlueConic REST API endpoints for use with AI coding assistants such as Cursor and GitHub Copilot in VS Code. By running the client locally, you can securely access your tenant’s APIs on a per-user basis, making it easier to explore, retrieve, and analyze customer data directly in your coding environment.
Important: When you open your BlueConic tenant with MCP, you’re giving the model access to your environment. This means you should ensure you’re working with a trusted MCP host that handles data responsibly. If the host misuses the context, it could expose sensitive information. Always confirm that the MCP host does not use your data for training their models.
Key features:
Runs locally for each user.
Provides dynamic, read-only API access from your tenant’s OpenAPI spec.
Secured with OAuth2 tokens.
Works instantly with any BlueConic tenant.
Before you begin
Make sure you have the following:
Node.js (version 22.x or higher).
NPM (Node Package Manager).
BlueConic tenant with REST API access.
An MCP host like Cursor, VSCode Copilot or other MCP host that supports running local MCP servers.
Set up the BlueConic MCP Client
Obtain OAuth credentials
Log in to your BlueConic tenant.
Go to Settings > Access management > Applications.
Create a new application with client credentials enabled.
Grant the read scopes that you want the MCP extension to use.
Copy the Client ID and Client Secret for use in your configuration.
The configured “run as user” permissions combine with the application scopes to determine access.
Integration with AI Tools
Cursor
Add the following to your .cursor/mcp.json:
{
"mcpServers": {
"blueconic": {
"command": "npx",
"args": ["@blueconic/blueconic-mcp"],
"env": {
"BLUECONIC_TENANT_URL": "https://yourtenant.blueconic.net",
"OAUTH_CLIENT_ID": "your_client_id_here",
"OAUTH_CLIENT_SECRET": "your_client_secret_here"
}
}
}
}
VS Code GitHub Copilot
Add to your VS Code settings mcp.json:
{
"servers": {
"blueconic": {
"name": "BlueConic MCP Server",
"description": "BlueConic MCP Server",
"command": "npx",
"args": ["@blueconic/blueconic-mcp"],
"env": {
"BLUECONIC_TENANT_URL": "${input:blueconic-tenant-url}",
"OAUTH_CLIENT_ID": "${input:blueconic-oauth2-client-id}",
"OAUTH_CLIENT_SECRET": "${input:blueconic-oauth2-client-secret}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "blueconic-tenant-url",
"description": "BlueConic tenant URL, e.g.
"password": false
},
{
"type": "promptString",
"id": "blueconic-oauth2-client-id",
"description": "BlueConic OAuth2.0 Client ID",
"password": true
},
{
"type": "promptString",
"id": "blueconic-oauth2-client-secret",
"description": "BlueConic OAuth2.0 Client secret",
"password": true
}
]
}
Claude Desktop
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"BlueConic": {
"command": "npx",
"args": ["-y", "@blueconic/blueconic-mcp"],
"env": {
"BLUECONIC_TENANT_URL":
"OAUTH_CLIENT_ID": "xxxxxxxx",
"OAUTH_CLIENT_SECRET": "xxxxxx"
}
}
}
}
`
Example prompts
Once configured, you can use natural language prompts to query your tenant:
“Get all segments from my BlueConic tenant and show me the commonalities.”
“Show me profiles in the ‘high-value-customers’ segment.”
“Retrieve 1000 profiles from the all visitors segment and summarize key insights.”
Example results