MCP tools — the full server surface
The MCP setup guide gets you connected and
covers the six developer tools. This page is the full map: one SSE
connection at ${api_url}/api/mcp/sse exposes three layers of capability,
all scoped to the token’s tenant + user — you only ever see what you have
access to.
The three layers
Section titled “The three layers”- Developer tools — discover, validate, scaffold (the setup guide’s six).
- Your business-skill catalog — every integration your tenant has connected, callable as a tool.
- Goal / session / app tools — the platform-native tools a coding session uses to read its goal, commit code, and read/write app data.
The catalog is dynamic: a tool appears only when its integration is
connected for your tenant. Connect Odoo and the odoo_* tools appear; connect
LinkedIn Ads and the linkedin_ads_* tools appear. list_skills always
reflects the live set.
1. Developer tools
Section titled “1. Developer tools”Full detail in the MCP setup guide. In short:
| Tool | Purpose |
|---|---|
list_skills | Every skill the platform knows, filterable by category |
get_skill_docs | Full reference for one skill — input + output schemas, scopes, risk level |
validate_manifest | The same validator linkworld deploy runs |
search_examples | Grep examples/ for patterns |
lint_app | Static checks across manifest + code |
scaffold_app | Generate a new app from a template |
Inside the Linkworld /chat assistant these carry a dx_ prefix
(dx_list_skills, …); over MCP they’re unprefixed.
2. Your business-skill catalog
Section titled “2. Your business-skill catalog”The same server exposes every business skill your tenant has configured as
a directly callable tool. This is the large surface — a fully-connected tenant
sees 150–300 tools. You don’t enumerate them by hand: call list_skills to see
the live set and get_skill_docs for one skill’s exact input/output schema.
Grouped by domain (each is a family of tools — connect the integration to make them appear):
- ERP & business documents — Odoo, Business Central, lexoffice; create invoices / quotes / delivery notes, render PDFs, look up prices, manage customers & items
- Microsoft 365 & Google — email (read / search / reply / drafts / triage), calendar, Drive & OneDrive, Teams
- Messaging & voice — WhatsApp (Business + personal), phone calls (Twilio / ElevenLabs), transcription
- Social — X, LinkedIn, Facebook & Instagram, Reddit — post, read comments, analytics
- Ads — Meta, Google, and LinkedIn Ads — campaigns, ad sets, creatives, budget, launch / pause, insights
- Marketing & media — produce campaign creatives, schedule posts, refresh metrics; generate images and video (Kling, HeyGen avatars, Remotion), stock imagery, diagrams
- Web & site — a headless browser (navigate, click, fill, screenshot, read console errors), web search, Vercel deploys, native website edits, SEO & GEO audits
- Dev & repos — GitHub, ClickUp, Figma, code & symbol search
- Knowledge & data — RAG collections (query / upsert / list), booking & appointments, CAD/DXF analysis, Excel / PDF / document generation, the per-app key-value store
Only the tools your tenant has connected are live; the rest simply aren’t in
your list_skills result.
3. Goal, session & app tools
Section titled “3. Goal, session & app tools”These are the platform-native tools — always available over the same connection, no integration required. A coding session running inside the Linkworld compute VM connects through this exact MCP path, which is how it reads its goal, commits, and opens a PR.
Goals & projects
| Tool | Purpose |
|---|---|
mcp_goal_status | A goal’s status, blockers, and dependencies |
mcp_goal_plan | The implementation plan + child phases |
mcp_goal_reviews | AI review findings for a goal |
mcp_execution_plan | The project’s dependency DAG with ready markers |
Coding sessions
| Tool | Purpose |
|---|---|
mcp_session_status | State of the current coding session |
mcp_session_commit | Commit the session’s work |
mcp_session_create_pr | Open a pull request |
mcp_register_runner / mcp_list_runners | Register / list the app’s live runners |
App data & artifacts
| Tool | Purpose |
|---|---|
read_app_records / write_app_records / delete_app_records | The app’s structured record store (supports paging + field/data filters) |
mcp_manage_data_feeds | The app’s data feeds |
mcp_set_company_products | Set a company’s product catalog |
mcp_verify_conversion_path | Confirm a built site’s funnel events fired |
Always on — even in a lean coding session
| Tool | Purpose |
|---|---|
request_human_action | Hand a step only a person can do to the owner, with the content to review attached |
request_capability | Ask the owner to connect a channel the app needs |
web_browser_* | Drive a real browser to test the thing you just built |
report_bug | File a bug from your session, same as the in-app report |
Two audiences, one connection
Section titled “Two audiences, one connection”The server tailors what it registers to the session:
- Chat & action sessions get the full business-skill catalog above — they run real work (send the email, launch the ad, post to LinkedIn).
- Code / build sessions get the lean platform layer (goals, session, app
records, dev tools) plus
request_human_actionand the browser — the 150+ business tools would only bloat every file-editing turn, so they’re left out.
Both connect to the same /api/mcp/sse endpoint; the token’s context decides
which layer you get.
Scoping & safety
Section titled “Scoping & safety”- Tenant + user scoped. The token binds to your account; every tool reads and writes only what you can. A partner app’s token is scoped to the capabilities its manifest declares.
- Credentials stay server-side. When a tool calls an external API (LinkedIn, Odoo, Meta), the platform resolves your stored OAuth credential and makes the call for you — the tool caller never sees the token.
- Token lifecycle: 24-hour TTL; re-mint with
linkworld mcp token. See the setup guide.