Connect your AI to PlanMyVisit with MCP, WebMCP and Poppy

MCP

Available

We provide 34 tools through MCP for compatible AI products, custom agents and new device experiences. They support planning before a visit and assistance while someone is there.

MCP endpoint: https://api.autoura.com/api/mcp

Sign in to give your personal AI agent access to the full set of 34 MCP tools, including visit knowledge, visit plans and preferences, subject to your account permissions. The same flow creates an account if you are new: you only need an email address and access to that inbox

Advanced settings

Normally, you only need the MCP endpoint. If your AI app asks for additional OAuth settings, use the details below:

Client ID: autoura-client
Authorization Endpoint: https://api.autoura.com/api/auth/oauth2/authorize
Token Endpoint: https://api.autoura.com/api/auth/oauth2/token
Scopes: files:read
Client Secret: Leave blank
Token Auth Method: Select none (PKCE only, recommended).

Profiles and registration

People can register an individual profile using an email address and connect their own AI agents.
AI agents can self-register or create and connect a profile on behalf of a person.
An agent registering for a person needs access to an email address for verification. This can be the person’s email address when authorised, or the agent’s own email address.
Register when the profile is new, or sign in when it already exists, then complete email verification before using protected tools.

WebMCP

Available

WebMCP is a simple way to connect PlanMyVisit to an AI, but browser adoption is still at an early stage.

All tools available through MCP are also available through WebMCP.
WebMCP does not support AI-agent self-registration. A person must sign in or sign up on this PlanMyVisit website.

OpenAI Codex

Codex in the ChatGPT desktop app is supported and tested with PlanMyVisit.

See the OpenAI Codex instructions

Other browsers

For developers only: Chrome and Microsoft Edge can expose and test WebMCP tools, but their standard AI assistants do not currently use them. This is not yet useful to consumers on its own, but it shows the direction browser support is taking.

Google Chrome 149 or later: WebMCP is in early preview. For testing, enable chrome://flags/#enable-webmcp-testing and relaunch Chrome. Chrome WebMCP documentation
Microsoft Edge 153 or later: WebMCP is experimental through an origin trial. Local testing can use edge://flags/#enable-webmcp-testing. Edge WebMCP release notes

Poppy — Personal Agent Protocol

MCP and AI conversations

Poppy lets a compatible personal agent connect to PlanMyVisit to help you plan and enjoy your visit

Before you sign in

Your personal AI agent can talk with our PlanMyVisit AI to discover supported places to visit and find out how PlanMyVisit can help. No account is needed for public venue search or general questions

“What can I visit in London?”
“Find supported places to visit near York”
“How can PlanMyVisit help me plan a day out?”

Public search provides venue summaries. Detailed visit knowledge, your saved visit plans and personal account information require sign-in

Once you sign in

Your personal AI agent can access detailed visit knowledge and your saved visit plans, and use our MCP tools to create and update visit plans, remember preferences and work with your current location. The tools available through Poppy depend on the permissions you grant during sign-in

“Show me my saved visit plans”
“Plan my visit to Buckingham Palace on [date] with [people’s names]”
“Add a note to my visit plan that we want a lunch break at noon”
“Remember I don’t like tomatoes”

Sign in when account access is needed. The same email-code flow signs you in or creates an account if you are new. You only need an email address and access to that inbox, then choose the permissions for your personal AI agent

Our PlanMyVisit AI answers questions; your personal AI agent uses MCP tools to make changes. Live human chat is not available

Poppy permissions and tools

Basic access is always included after sign-in. The six optional permissions start on and can each be turned off. These permissions apply to your personal AI agent’s MCP access through Poppy

Permission and scope	MCP tools
Basic accessplanmyvisit	`preferences_get`, `personal_data_export_request`, `companions_search`, `companion_profile_get`, `companion_invites_inbox`, `companion_invite_link_create`, `companion_invite_to_current`, `companion_invite_accept`, `companion_end_current`, `companion_block`, `companion_unblock`, `companion_disconnect`, `visit_venues_search`, `visit_knowledge_get`, `visit_provenance_get`, `visitplan_get`, `visitplans_search`, `content_gap_report`, `product_gap_report`, `characters_search`, `stop_get`, `stop_provenance_get`
Create visit plansvisitplans:create	`visitplan_new`
Update visit plansvisitplans:update	`visitplan_update`, `visitplan_note_new`, `visitplan_change_lead`, `visitplan_member_add`, `visitplan_member_state_update`, `visitplan_member_priorities_update`, `visitplan_member_remove`, `visitplan_delete`
Update preferencespreferences:update	`preferences_update`
Get my current locationlocation:read	`location_get`
Update my current locationlocation:update	`location_update`
View travel companions’ current locationscompanions:location:read	`companions_search`, `companion_profile_get` — allows shared current locations in these results

Poppy provides access to the full MCP tool set, subject to your account permissions and the switches above. Basic access includes companion management, data export requests and reports, as well as visit knowledge and viewing information

Nearest-companion search requires both location-viewing permissions. Travel companions must have enabled location sharing with you. Updating your location does not grant permission to read it back