BCMS MCP
Description
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update…
About
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update content entries, manage media files, and…
Details
- Author
- Unknown
- Categories
- Developer Tools, Other, AI, Productivity
Jump to
Connect any AI assistant to your BCMS instance and manage your CMS by talking to it. Through the Model Context Protocol (MCP), tools like Cursor, Claude, VS Code, and others can design your content model, write and translate real content, and manage media - directly in your instance, scoped to a key you control.
Most CMS integrations let an AI fill in fields. BCMS MCP lets it build the CMS too - create templates, groups, and widgets, then populate them with fully formatted, internally linked, multilingual content. Model and content, in one conversation.
-
Query and explore your content structure
Create new content entries with AI-generated content
Get intelligent suggestions based on your content model
-
Design your content model - create and edit templates, groups, and widgets, including typed fields and entry/group pointers. "Create a Blog template with title, slug, an author group, and a rich-text body."
Publish real content - entries with headings, lists, code blocks, embedded widgets, images, and internal links to other entries/media. "Write a 600-word post on headless CMS, add H2 sections and a code block, and link the 'About' entry."
Go multilingual - manage locales and author per-language content in one pass. "Add German and translate the three latest blog posts."
Manage media - organize directories and upload files via a returned upload URL (handles large files). "Create a 'Blog Images' folder and give me an upload URL for the hero image."
Stay safe - read entry statuses, full change history, and trash for auditing and recovery. "Show the change history for this entry."
Your assistant discovers the exact tools automatically on connect - no need to memorize tool names.
In BCMS, go to Settings → MCP and Create MCP Key
{ "mcpServers":{ "bcms":{ "url":"https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY" } } }
Per-client setup snippets (Cursor, Claude, Claude Code, VS Code, Codex, Gemini CLI, Windsurf, Goose, and more) are available right inside BCMS on the MCP page.
-
Least privilege - create separate keys per use case or teammate; rotate them periodically.
Key format - keyId.keySecret.instanceId. A "key not found" error almost always means a malformed or revoked key.
-
Endpoint: POSThttps://app.thebcms.com/api/v3/mcp?mcpKey={MCP_KEY}
Transport: Streamable HTTP with session management (mcp-session-id header).
Rate limits: same as the BCMS API, tracked per key.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
The Laxis MCP Server connects Laxis - the AI meeting note taker and voice dictation tool for professionals to Claude and other AI tools through the Model Context Protocol. Your assistant can search and read your meeting transcripts, summaries, and participants directly in chat — turning every conversation you've recorded into context your AI can reason over.
Pinako AI Bridge connects your browser tabs, bookmarks, Pinako libraries and notes to Claude, Cursor, and other desktop AI clients, so your agent can query them, organize them, and move information between Pinako and your other tools and services.
Native macOS API client with embedded MCP server. 31+ tools for AI-assisted API development. Schema extraction ensures AI never sees real credentials or PII. Supports Claude Code, Claude Desktop, Cursor
Local macOS MCP server that finds API keys and secrets leaked into Claude Code, Cursor, Copilot, and other AI tool transcripts. 9 tools: findings list, boolean secret detection, placeholder-only redaction (sieve://project/key), vault-backed command execution. No plaintext secrets ever returned.
Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.
After Effects MCP is a full-featured automation bridge that connects AI clients (like VS Code, Claude Desktop, and Claude Code) to Adobe After Effects through MCP, enabling scripted control of compositions, layers, effects, keyframes/graph easing, presets, markers, audio levels, waveform analysis, and effect discovery via a live bridge panel.
Project management your AI can actually run — connect Claude, ChatGPT, Cursor & Codex to one board over MCP.
AIOProductOS spine over MCP — customers, revenue, feedback, work, analytics on one typed record.
The memory layer for AI coding tools. Local-first, semantic, 9 MCP tools with consolidation and project scoping. Works with Claude Code, Cursor, Windsurf & any MCP client.
Track app-store keyword rankings, rank history, listing metadata, engagement, reviews, and competitors across iOS, macOS, Google Play, and Microsoft Store.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
