Add developer reference page for Fulcrum MCP & AI Toolkit - #89
Conversation
Adds docs/DOCUMENTATION/developer-information/mcp-ai-toolkit.md covering the /mcp endpoint (regions, transport, auth, all 56 tools across 17 categories) and AI Toolkit installation, for developers and agent clients — distinct from the existing Intercom help article aimed at end users. Registers the page in the Developer Information sidebar order.
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Pull request overview
Adds a new developer-focused reference page for Fulcrum MCP and the Fulcrum AI Toolkit, and wires it into the Developer Information sidebar ordering.
Changes:
- Added
mcp-ai-toolkit.mdwith endpoint/protocol/auth details, a tool reference table, installation commands, and known limitations. - Updated
_order.yamlto include the newmcp-ai-toolkitpage in the Developer Information navigation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 9 comments.
| File | Description |
|---|---|
| docs/DOCUMENTATION/developer-information/mcp-ai-toolkit.md | New developer reference page documenting MCP endpoints/auth, tool catalog, Toolkit install steps, and limitations. |
| docs/DOCUMENTATION/developer-information/_order.yaml | Adds the new page slug to the ordered nav list for this section. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
7e0cfa4
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
Jira: FLCRM-21791
Summary
Adds a developer-facing reference page for Fulcrum MCP and the Fulcrum AI Toolkit:
docs/DOCUMENTATION/developer-information/mcp-ai-toolkit.mdThis is deliberately a separate document from the customer-facing Intercom help article — Fulcrum MCP & AI Toolkit (Labs) — which is written for non-technical end users (conversational tone, setup walkthroughs, troubleshooting). This page is terse, tables/code-first, and assumes the reader (human developer or LLM/agent client) already knows MCP, JSON-RPC, and Bearer auth. The new page links to the Intercom article for readers who want the guided version, and vice versa should be added on that side.
Placement
Added as the 5th child page under Developer Information, alongside the existing Webhooks, Sharing Data, URL Actions, and Desktop Sync pages — same audience and "another way to integrate with Fulcrum" framing. (Note: the brief that kicked this off assumed 3 existing siblings; there are actually 4 — Desktop Sync was already there.)
Front matter, category, and file-naming convention were matched exactly against the sibling pages in this directory (confirmed against
webhooks.md,data-shares.md,url-actions.md,desktop-sync.md) — noauthorfield, since none of those four have one.robots: indexwas chosen to matchdata-shares.md/url-actions.md(the two non-hidden, indexed siblings) rather thanwebhooks.md/desktop-sync.md'snoindex.The new page's slug (
mcp-ai-toolkit) was appended todocs/DOCUMENTATION/developer-information/_order.yaml, since that specific file is currently kept exhaustive (lists all 4 existing siblings). Note this isn't true repo-wide — e.g.docs/App Extensions/app-extension-examples/_order.yamlonly lists 2 of its 5 files, and PR #87 (which added a new page there) didn't touch it — so ordering discipline appears to be per-directory, not enforced globally. I followed this directory's own convention rather than the looser one elsewhere.Tool reference table
The full 56-tool reference (grouped into the 17 categories) was generated from a live
tools/listcall againsthttps://mcp.fulcrumapp.com/mcp, run 2026-09-11 against a real Fulcrum org token, not written from memory or docs. Please re-verify tool names/descriptions/counts haven't drifted if there's been a meaningful gap before merging — a note to that effect is also in the page itself.Scope notes
/appis not mentioned or linked anywhere on this page, per the instruction that it's a real but unsupported/narrower endpoint (a separate fix is apparently already in flight on thefulcrumapp/fulcrum-ai-toolkitrepo's own docs, which as of this writing still reference/appin its README's "Connect Fulcrum App MCP" section — flagging in case that's news, since it's the opposite of what should be publicly pointed at).initializesession error) are documented twice as instructed: inline in the Auth section where an implementer needs it while building, and again as a scannable table in "Known limitations (Labs)".fulcrumapp/fulcrum-ai-toolkitREADME (Claude Code, Codex, GitHub Copilot CLI, generic skills loader), stripped of "why" framing, plus the two unsupported-today rows (Claude Desktop chat/Cowork, ChatGPT) called out in the task brief.Test plan
rdme(or ReadMe's PR preview, if configured) and confirm the page renders correctly — tables, code fences, and callout boxes in particular.tools/listcall if this sits for a while before merge.