PocketPapiHelp Center

Help Center · MCP

Connect your AI workspace to PocketPapi.

Use MCP to let Codex, OpenCode, and other compatible agents read sites, reviews, conversations, leads, and operational activity from one secure installation.

Manage MCP / API · Create an MCP token Administrator access required

Enable MCP in four steps

1
Create an access token
An administrator creates a bearer token and stores it as a server secret.
2
Connect your MCP client
Use the remote endpoint below in Codex, OpenCode, or another MCP client.
3
Choose a site scope
Site-scoped tools require a site ID for reviews, activity, conversations, tickets, and Zernio operations.
4
Connect Google and Zernio
Connect a verified Google Business Profile through Social API Setup before requesting reviews.

Remote MCP connection

Endpoint

POST https://pocketpapi.com/mcp

Authentication header

Authorization: Bearer YOUR_TOKEN

OpenCode-style configuration

{"mcp":{"sitecommander":{"type":"remote","url":"https://pocketpapi.com/mcp","headers":{"Authorization":"Bearer YOUR_TOKEN"}}}}

What you can connect

Use the read tools to inspect the projects and sites owned or shared with the token creator, status, tasks, activity, conversations, chat messages, support tickets, ticket messages, reviews, sender profiles, BIMI checks, and Zernio accounts. The live-chat tools read and reply to visitor conversations that staff see in Support Inbox and the Command Center action center.

Connect a customer site

For a site's own server-side forms, leads, subscriptions, or MCP client, open that site's details in the authenticated command center and choose Connect site to command center. PocketPapi creates a separate site-scoped token with the same one-time reveal and rotate behavior. It can only reach that site, and every call appears in central Audit Logs and the command-center activity view.

Read the server integration contract →

PocketPapi site connections

Site owners can connect an authorized site to the shared PocketPapi iOS and Android client from the Apps page. Public sites appear in the mobile chooser; private sites require a one-time configuration code. PocketPapi uses its own site-scoped user session for leads and chat, so an MCP token should never be placed in the mobile app.

Read the PocketPapi API contract →

Effects tools

The public catalog currently contains 63 copyable recipes, including advanced scroll-driven motion, text systems, 3D/perspective interactions, form feedback, dialogs, and free MIT library starters. Use the read-only MCP tools to search, fetch, and compose a recipe before writing new animation code.

sitecommander_effects_search
sitecommander_effects_fetch
sitecommander_effects_compose

Browse and preview every effect in the Help Center →

See the complete discovery and endpoint reference →

Sender photos & BIMI

Use sitecommander_mail_profiles to list sender identities and sitecommander_mail_profile_upsert to manage a public custom photo. Use sitecommander_bimi_prepare, sitecommander_bimi_status, sitecommander_bimi_verify, and sitecommander_bimi_record to prepare and verify a domain logo. These tools do not change DNS or send email, and provider-owned Gmail/Microsoft 365 photos remain outside PocketPapi’s control.

Keep the token private

Never expose bearer tokens. Use MCP and the API from your server or AI-client configuration. Do not put a token in public HTML, browser JavaScript, or a client-side app bundle.