TSC: MCP Enablement Program – Phase 0

[hdamker]

Status: Draft - for TSC discussion
Purpose: TSC input to launch MCP enablement
Context: superseding Governance #203, which will be closed with a pointer here. Whitepaper review was tracked in Governance #202.

1. Outcome

• CAMARA API Design Guide enhanced with MCP-friendly documentation requirements (AI-readable descriptions, consistent parameter naming, actionable error messages)
• CAMARA publishes MCP security/consent guidance for MCP server implementations
• CAMARA defines "MCP-ready" criteria for APIs
• CAMARA delivers pilot MCP tool definitions demonstrating the end-to-end process

2. Scope (Phase 0)

Pilot API Set (tbd, 1-2 APIs to be swapped if needed):

1. Number Verification (fraud/onboarding signal)
2. SIM Swap (fraud signal)
3. Quality on Demand (lifecycle/stateful)
4. Location Verification (decision signal/privacy-friendly)

Criteria for selection: near-term business value, cross-operator interoperability likelihood, mature APIs, cover different patterns (subscriptions/event only if we can staff it), manageable security/privacy risk

Deliver:

• API Design Guide enhancements (v0.1)
• MCP Security & Consent Note (v0.1)
• MCP Readiness Checklist (v0.1)
• Tool Definition Guide (v0.1)
• Pilot tool definitions

Out of scope (Phase 0): Subscription APIs (e.g. Geofencing), reference MCP server implementations, formal certification

3. TSC Decisions Needed

• Pilot APIs: Agree and confirm pilot API set
• MCP Activity / Task Force: continue to support / coordinate the activities?
• Tool definitions hosted: Centrally (Commonalities) vs. per-API repos vs. new repo
• "MCP-ready" criteria ownership: Commonalities vs. Release Management vs. joint
• Security guidance location: New section in Security Profile vs. standalone doc in ICM

4. Workstreams & Sponsors

WS	Focus	Sponsor
WS1	API Design Guide Enhancements	Commonalities
WS2	Security & Consent Guidance	ICM
WS3	Readiness Checklist	Release Management
WS4	Pilot Tool Definitions	API Sub Projects

5. Phase 0 Deliverables (Child Issues)

• API Design Guide – Improve API Design Guidelines for MCP/Agent readiness (Commonalities)
• MCP Security/Privacy/Consent guidance for MCP tool servers v0.1 (ICM)
• MCP Readiness Checklist v0.1 (Release Management)
• Pilot: Number Verification API for MCP readiness
• Pilot: SIM Swap API for MCP readiness
• Pilot: Update Quality on Demand API for MCP readiness
• Pilot: Update Location Verification for MCP readiness
• CAMARA Tool Definition Guide v0.1 (Commonalities)

6. Links

• CAMARA + MCP Position Paper
• Governance #203 (to supersede)
• Commonalities Discussion #554
• MCP Specification

[bigludo7]

Hello @hdamker
Look very good for me. As regular contributor of Sim Swap, Number Verification, device location and Commonalities happy to contribute to "CAMARA API Design Guide enhanced with MCP-friendly documentation requirements" topic.