MCP Connector Reference for AI Agent Workflows

This documentation explains the Oneflash MCP runtime, governance rules, module capabilities, and representative tools available for private tenant AI agent workflows.

Overview

Oneflash MCP is not a public marketplace of downloadable servers. It is a governed connector layer inside Oneflash business systems. AI agents can read business data, prepare changes, upload files, and submit governed write requests through tenant-scoped MCP tools.

237

Current MCP tools in repo

8

MCP-enabled modules

allow / check / disallow

Governed execution modes

Runtime Contract

Oneflash MCP tools run through a private tenant runtime. The visual docs explain the rules, while the tool-level list is maintained separately from a CMS collection.

View public tool list

Runtime Contract

Endpoint
POST /api/mcp
Auth
x-api-key
Mode
private tenant MCP with governed writes

Basic Rules for AI Agents

These rules are more important than the tool list. Agents should follow them before making any read, write, upload, or approval request.

Use the MCP endpoint, not tenant headers

Agents should call the JSON-RPC MCP endpoint. Tenant context is derived from the API key; callers must not self-report tenant or workspace headers.

POST /api/mcp with x-api-key

Read before write

Before calling a write tool, agents should read the relevant schema, item keys, language keys, and base version token from the matching read tool.

list/get -> prepare write -> approval/status

Do not retry pending writes

If a write tool returns pending_approval, agents should poll the action request instead of submitting the same write again.

core.get_action_request_status

Upload is a two-step flow

Agents should create an upload session, upload the file, then call media.get_upload_session_result. The result is the source of truth for media_id, URL, and file format.

create_upload_session -> HTTP upload -> media.get_upload_session_result

MCP-enabled Modules

The public index should show module capability first, then link to per-module references.

ModuleStatusToolsReadWriteCapability

WebsiteManager

/docs/mcp/tools/website-manager		Available66Website pages, collections, metadata, Google schema, upload sessions, global content, and deploy-oriented content workflows.

ContentGrowth

/docs/mcp/tools/content-growth		Available58Campaigns, claim rules, personal insights, content records, online listings, tracking configs, and append-only tracking results.

EducationCenter

/docs/mcp/tools/education-center		Available42Students, courses, classes, enrollments, attendance, invoices, payment proofs, learning resources, notices, and leave requests.

ProductCatalog

/docs/mcp/tools/product-catalog		Available17Product items, categories, product types, price and stock updates, media attachment, and archive flows.

Connector Availability Map

This table separates real MCP tools from app and industry connector plans. Planned rows describe intended connector families, not callable production endpoints.

Website Builder and CMS

App / WebsiteManager

Available
MCP tools
66 WebsiteManager tools
AI-readable wording
Available as governed MCP tools for website content, collections, metadata, schema, upload, and deploy workflows.
Notes
Use the real WebsiteManager tool reference.

AI SEO / Content Operations

App / ContentGrowth

Available
MCP tools
58 ContentGrowth tools
AI-readable wording
Available for campaign memory, claim rules, content records, online listings, and AEO tracking workflows.
Notes
Use the real ContentGrowth tool reference.

Education Center Operations

Industry / EducationCenter

Available
MCP tools
42 EducationCenter tools
AI-readable wording
Available for students, courses, attendance, invoices, payment proof review, resources, notices, and leave requests.
Notes
Use the real EducationCenter tool reference.

Product Catalog

App / ProductCatalog

Available
MCP tools
17 ProductCatalog tools
AI-readable wording
Available for product items, categories, product types, price and stock updates, media attachment, and archive flows.
Notes
Use the real ProductCatalog tool reference.

CRM Customer Relationship Management

App / Sales workflow

Planned
MCP tools
0 exposed MCP tools
AI-readable wording
Planned connector family for leads, customers, follow-up tasks, pipeline updates, and sales approval workflows.
Notes
Do not describe as callable MCP endpoints until implemented.

WhatsApp Business API

App / Communication workflow

Planned
MCP tools
0 exposed MCP tools
AI-readable wording
Planned connector family for message preparation, conversation context, reminders, and human-approved customer communication.
Notes
Customer-facing send actions should remain approval-controlled.

Online Booking

App / Scheduling workflow

Planned
MCP tools
0 exposed MCP tools
AI-readable wording
Planned connector family for availability checks, booking preparation, schedule changes, and approval-safe reminders.
Notes
Do not publish fake booking tool names before implementation.

Inventory Management

App / Operations workflow

Planned
MCP tools
0 exposed MCP tools
AI-readable wording
Planned connector family for stock lookup, reorder preparation, low-stock alerts, and governed inventory updates.
Notes
Can later link to ProductCatalog if stock fields become the first implemented path.

Retail and Wholesale Solution

Industry

Design Draft
MCP tools
0 exposed MCP tools
AI-readable wording
Designed workflow area for order, catalog, pricing, customer, and inventory connector planning.
Notes
Reference as industry workflow planning, not available MCP tools.

F&B Management Solution

Industry

Design Draft
MCP tools
0 exposed MCP tools
AI-readable wording
Designed workflow area for menu, booking, order, stock, invoice, and reminder connector planning.
Notes
Reference as industry workflow planning, not available MCP tools.

Workflow Examples

Website content update

A safe sequence for AI agents editing website content through WebsiteManager MCP tools.

  1. 1Call website.list_websites and choose a website_id.
  2. 2Call website.list_pages and website.get_page_content for the exact page.
  3. 3Use section_key, field_key, language, and base_version_token from the read response.
  4. 4Call the matching write tool and poll the action request if the result is pending_approval.

Media upload

A safe sequence for image and file uploads before writing media references into content fields.

  1. 1Read the target page, collection item, or product item first.
  2. 2Create the correct upload session for the target field.
  3. 3Upload the file to the returned upload_url.
  4. 4Call media.get_upload_session_result and use the returned media_id or URL as the final truth.

AI-readable Files

The visual docs page should be paired with markdown and manifest routes so AI agents can ingest the same information without relying on layout.

/llms.txt
/llms-full.txt
/docs/mcp/index.md
/docs/mcp/manifest.json
/docs/mcp/tools/website-manager.md
/docs/mcp/tools/content-growth.md