{"slug":"platform/11-developer-platform","title":"11 — MCP, ADK, SDK, APIs, and Developer Platform","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/11-developer-platform.mdx","bytes":2790,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Canonical boundaries; publication states vary\n\n## Public MCP\n\n`services/mcp-connector/` owns the exact nineteen semantic tools:\n\n1. `get_my_continuity`\n2. `get_active_context`\n3. `get_my_focus`\n4. `get_context`\n5. `get_changes`\n6. `get_related`\n7. `get_history`\n8. `get_commitments`\n9. `get_decisions`\n10. `get_permitted_memory`\n11. `get_relevant_knowledge`\n12. `ask_twin`\n13. `assign_twin`\n14. `get_prepared_work`\n15. `get_available_actions`\n16. `prepare_action`\n17. `get_action_plan`\n18. `approve_action`\n19. `store_in_spine`\n\nAny different public inventory is a stop-ship defect.\n\nThe tool contract is packaged in two ways:\n\n- **IW-Spine-Network Plugin** for plugin directories: MCP-backed app, focused\n  sandboxed widgets, workflow skills and optional templates inside the AI host;\n- **IW-Spine-Network MCP** for MCP registries: remote server, optional MCP App\n  widgets, meaningful text/JSON fallback and browser Workbench launch.\n\nUI resources do not increase the nineteen-tool inventory.\n\n## ADK and agents\n\nThe ADK defines governed agent registration, context scope, tool scope, memory\nscope, approval boundary, status, evidence, stopping rule, and escalation. Agents\ndo not access the canonical database directly and cannot self-promote output.\n\n## SDK responsibilities\n\nPublic SDKs should remain small and versioned:\n\n- authentication and tenant-aware API clients;\n- semantic Spine and Workbench contracts;\n- MCP client/server helpers;\n- capability and connector conformance helpers;\n- governed agent registration;\n- event envelopes;\n- canonical schema types.\n\nPackage names, public APIs, licensing, support, changelog, semantic versioning,\nsecurity policy, examples, and compatibility tests must be ready before public\npublication.\n\n## API boundary\n\nGateway is the public control boundary. Product clients do not call provider\nSDKs, storage, Nango, or internal MCPs directly. Public APIs use verified\nidentity, tenant scoping, versioned contracts, rate limits, structured errors,\naudit correlation, and revocation.\n\n## Skills and plugins\n\nA distributable skill includes:\n\n- complete `SKILL.md`;\n- triggers and intended user;\n- required context and evidence;\n- permitted and prohibited actions;\n- identity, tenant, Governance, and Hermes boundaries;\n- failure and escalation behavior;\n- examples, tests, owner, and version.\n\nPlugins package capabilities; they do not create a second Platform or bypass\nthe public Spine Network contract. An embedded widget cannot inspect host DOM,\ncookies or unrelated app credentials.\n\n## Publication state\n\nCode-backed packages may be Implemented while still private. “Published” means a\nversioned artifact is publicly retrievable, documented, install-tested, and\nsupported.\n"}