Developers
MCP integration
Connect an AI assistant to the Retail Compliance Community through the Model Context Protocol (streamable HTTP). The MCP server sits on top of the Community Agent API — same data, same rules.
Endpoints
Member connection (recommended, OAuth): the assistant signs the member in once and can then act for them in later conversations.
https://fiscal.community/mcpPublic connection (no sign-in): browsing plus an email-code fallback for assistants without OAuth support.
https://fiscal.community/mcp/v1Connecting with OAuth (recommended)
- Add the member connection URL as a remote MCP server / custom connector in an assistant that supports MCP OAuth.
- The assistant opens a Fiscal Community page. Enter your business email and the one-time code we email you.
- Review what the assistant may do and choose Approve.
- From then on, the assistant can use your Community account in new conversations until the authorization expires or you disconnect it — no new code needed.
Connecting only authorizes the assistant. It does not register you for any event and does not accept any Terms of Use; the assistant must ask you to confirm each registration and each legal acceptance in the conversation.
OAuth changes assistant authorization only. Website login, Community membership and Forum registration on the website work exactly as before.
Disconnecting
Open My Account → Connected AI assistants and choose Disconnect. This immediately stops the assistant from acting for you. Removing the connector in the assistant also stops it using your account. Your membership and registrations stay.
Registration sequence and legal acceptance
- The member chooses a Forum or Community Day.
- The business email is verified first — through OAuth or the email code. Before that, the assistant does not show legal texts and cannot learn whether the email belongs to a member.
- After verification the server states what applies to this person:
- New member: the assistant collects the profile, presents the current Terms of Use and Privacy Policy with their versions, obtains explicit acceptance and acknowledgement, then creates the membership and registers for the chosen event.
- Active member, acceptances current: no legal texts and no new acceptance — the assistant shows the event and asks you to confirm the registration.
- Updated legal version: only the changed version is presented and your choice is recorded before registering.
- Inactive member: the assistant files a restoration request; no duplicate account is created.
Optional marketing consent is separate and never requested as part of registration.
Fallback: email code in the chat
For assistants that cannot use OAuth, use the public connection. The assistant asks for your business email, you type the 6-digit code from your inbox into the chat, and the assistant receives a single-use proof valid for 15 minutes.
Each proof covers exactly one member action (for example joining and registering for the chosen event in one step, or one registration, or listing your registrations). A further action needs a new code. Nothing is remembered: a new conversation always requires fresh email verification. The fallback does not provide a persistent login, and no reusable key or token is ever shown in the chat.
Available tools
Public tools work on both endpoints without sign-in. Member tools on the OAuth endpoint act for the signed-in member; on the public endpoint they require a fresh single-use email proof.
| Tool | Access | Purpose |
|---|---|---|
| get_community_info | Public | Community overview, eligibility and legal references. |
| list_upcoming_forums | Public | Upcoming Retail Compliance Forums; optional filters: topic, language, from and to (ISO 8601 dates), alone or combined. |
| get_forum_details | Public | Full details for a single Forum. |
| get_community_day | Public | Current Community Day details. |
| get_registration_requirements | Public | Profile fields and legal version identifiers. Legal texts are shown only after verification, when actually required. |
| get_my_membership_status | Member read (OAuth) | Called first after sign-in: membership state and the legal action actually required for this member. |
| join_community | Member action | New members only: create the membership after explicit acceptance of the legal texts; optionally register for an event. |
| accept_current_legal_versions | Member action (OAuth) | Only when re-acceptance is required: record acceptance of updated Terms and Privacy Policy. |
| register_for_forum | Member action | Register for a Forum after explicit confirmation. A member has one registration per Forum: repeat calls, even with a new idempotency key, return already_registered with the original registration and link. |
| register_for_community_day | Member action | Register for Community Day after explicit confirmation. |
| get_my_registrations | Member read | The member's own registrations. |
| get_forum_join_access | Member read | The member's own personal Forum link: link_available_room_not_yet_open (with room_opens_at, about 30 minutes before start), open, ended or link_unavailable. |
| start_email_verification | Fallback only | Send a one-time code to the business email. |
| verify_email_code | Fallback only | Confirm the code; returns a single-use proof plus membership state and required legal action. |
| recover_membership | Member action | Inactive members only: request restoration instead of creating a new account. |
Registration tools return the stored state — registered, already_registered or pending — rather than just confirming that a request was sent.
Supported assistants
Any assistant that supports remote MCP servers over streamable HTTP can use the public connection. Step-by-step instructions for specific assistants will be published here once they have been confirmed against a working connection.
Relationship to the Agent API
Every MCP tool maps to a Community Agent API operation. If you are building your own integration rather than connecting an assistant, use the REST API directly.
Open the API documentation