Enable MCP in five steps
Use browser OAuth when your client supports it. Otherwise, a scoped token is available: Create an MCP token.
Add the PocketPapi marketplace, then install
pocketpapi-codex-agent. It contains the shared Codex skill and MCP connection.Add the remote endpoint below in Codex, OpenCode, or another MCP client and complete browser approval.
Site-scoped tools require a site ID for reviews, activity, conversations, tickets, and Zernio operations.
Configure your personal MCP servers in MCP Studio and connect any PocketPapi service accounts your workflow needs.
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"}}}}
Codex plugin and MCP setup
MCP Studio’s Install plugin + fill Codex action copies a reviewable setup prompt and opens Codex only after confirmation. The browser cannot edit your local Codex configuration on its own. After installing, enable the bundled PocketPapi MCP server in Codex Settings → MCP servers. If your Codex surface cannot configure authentication for bundled servers, use the standalone command below as a fallback, then restart Codex. Keep only one PocketPapi entry enabled:
codex plugin marketplace add https://github.com/stouterenterprises/SiteCommander.git --sparse tools/pocketpapi-marketplace codex plugin add pocketpapi-codex-agent@pocketpapi codex plugin marketplace list codex plugin list codex mcp add pocketpapi --url https://pocketpapi.com/mcp
Add https://pocketpapi.com/mcp as the remote server. Your client discovers PocketPapi authorization, opens a browser sign-in, and asks you to approve the selected project scope. Verify with codex mcp list, sitecommander_status, and sitecommander_mcp_version. A manual POCKETPAPI_MCP_TOKEN is available from the MCP Studio dialog only for clients that cannot complete OAuth.
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 your other MCP servers
Connected servers are optional plugins. Your chat can check the design MCP catalog, explain a useful option, and ask before you enable or use it. Connect n8n, MarkItDown, Context7, GitHub, Playwright, or Chrome DevTools from MCP Studio with your own endpoint and account credentials. PocketPapi encrypts credentials, discovers remote tools, and makes them available through the same MCP connection in your Codex projects. Use public HTTPS Streamable HTTP endpoints; local stdio servers need a secured remote endpoint that you host. OAuth read-only clients can call read-only remote tools; write tools require the client’s mcp:write grant. For animation design, use PocketPapi’s built-in effects catalog, or connect SVGator and Figma directly in a supported OAuth-capable client because PocketPapi does not broker their interactive OAuth sign-in.
- Animation authoring: SVGator MCP creates editable SVG animation projects. The connector is included with every plan; animated exports require a paid plan.
- Design context: Figma MCP reads design context and supports design-to-code workflows for clients in Figma’s MCP catalog.
- Browser performance: Chrome DevTools MCP offers free, open-source Chrome debugging and performance traces; Playwright MCP supports browser-based layout and interaction checks. Both need a browser runtime and a secured remote endpoint to route through PocketPapi.
- Website motion and speed: PocketPapi’s built-in effects MCP tools prepare reduced-motion-aware recipes and staged effects, while its PageSpeed tool audits public pages.
Site Studio update check
After browser authorization, identify the authorized customer site. Site Studio MCP supports page content and SEO, navigation, page roles, every supported no-AI block, approved-media image replacement, managed effects, forms, galleries, protection, and PageSpeed audits for public pages. File changes stay in staging and return a preview. Link lists and inserted links accept Amazon/eBay tracking IDs, use the site Shop connection before PocketPapi central Shop when a link ID is blank, and can add an HTTPS profile to the social bar. Affiliate links include sponsored/nofollow attributes and nearby disclosure copy. A missing or stale feature-pack marker does not block routine edits or authorize a full upgrade. Use bootstrap and pack upgrade only for separately requested setup. Production stays unchanged until the owner approves the exact staged revision.
Discover pages with sitecommander_site_studio_pages. Use the matching Site Studio MCP tool for the requested edit. Every file write returns a preview URL and change_set_id. Review the exact revision, then ask for separate production approval. After approval, call sitecommander_site_studio_publish with that site_id, reviewed change_set_id, and confirm=true. Site Studio checks token scope and production deployment rights. Do not import this repository or upgrade the full pack for a routine edit.
Command cookbook
Paste these tool names or prompts into a connected MCP client. Start with the version check, keep site_id explicit, and ask for approval before sending messages or changing customer-facing data.
sitecommander_design_mcp_catalog {"query":"animation"}
sitecommander_external_mcp_connections
sitecommander_status
sitecommander_projects
sitecommander_sites
sitecommander_mcp_version {"site_id":123}
sitecommander_mcp_studio {"site_id":123}
sitecommander_site_bootstrap {"site_id":123}
sitecommander_accounts {"site_id":123}
sitecommander_leads {"site_id":123,"status":"new","limit":50}
sitecommander_clients {"site_id":123,"limit":50}
sitecommander_activity {"site_id":123}
sitecommander_conversations {"site_id":123}
sitecommander_messages {"conversation_id":456}
sitecommander_tickets {"site_id":123}
sitecommander_ticket_messages {"ticket_id":789}
sitecommander_mail_profiles {"site_id":123}
sitecommander_galleries {"site_id":123,"page":"home"}
sitecommander_gallery_save {"site_id":123,"name":"Gallery","page":"home","items":[]}
sitecommander_services {"site_id":123}
sitecommander_service_save {"site_id":123,"title":"Consultation","description":"Owner-provided service details","preview_page":"services"}
sitecommander_service_delete {"site_id":123,"id":456,"preview_page":"services"}
sitecommander_zernio_accounts {"site_id":123}
sitecommander_zernio_social {"site_id":123}
sitecommander_zernio_sync {"site_id":123}
sitecommander_business_network {"site_id":123}
sitecommander_easyapp {"site_id":123}
sitecommander_agents
sitecommander_scheduled_tasks
sitecommander_task_claim_local
sitecommander_task_complete_local {"run_id":456,"status":"completed"}
sitecommander_effects_search {"q":"scroll reveal"}
sitecommander_effects_fetch {"effect_id":"fade-up-reveal"}
sitecommander_shop_products {"site_id":123}
sitecommander_shop_orders {"site_id":123}
sitecommander_pos_catalog {"site_id":123}
sitecommander_pos_sync_health {"site_id":123}
Useful edit prompt: “On site 123, improve the existing page as a professional link-in-bio page. Keep verified branding and links, stage the edit in Site Studio, and return a preview link. Do not import the PocketPapi repository or install a full feature pack. Ask separately before publishing.” For a full managed-pack setup, name that separate scope explicitly and approve it before the agent stages the pack.
Scheduled Site and Local tasks
MCP Studio can create project/site-scoped recurring tasks. Site tasks run through PocketPapi’s bounded cPanel cron using the encrypted project provider; Local tasks are claimed by a connected Codex, Claude, or portable local runner and execute with that client’s own provider key. Call sitecommander_agents to discover enabled agents before linking one to a task. Every MCP response includes contract metadata, and the client should call sitecommander_mcp_version first so a changed contract is refreshed before the next run.
The administrator-controlled Agent Runner switch in Settings enables the server lane. One cPanel request runs a small batch of Site-mode agents and Site-mode MCP tasks, then exits; it never launches a permanent worker, desktop session, or browser on shared hosting. Built-in automations use deterministic server rules where possible, preserve project/site scope, write audit/run history, keep learning items reviewable, and leave external side effects behind the existing approval boundary. Follow the execution limits in your AccuWeb plan when choosing the cPanel interval.
sitecommander_mcp_version sitecommander_agents sitecommander_scheduled_tasks sitecommander_task_create sitecommander_task_claim_local sitecommander_task_complete_local
Configure one cPanel CLI job for /usr/local/bin/ea-php82 /home/stouter1/public_html/commander/app/Cli/agent-runner-cron.php. It reads the cron secret from PocketPapi’s server-owned config, so no secret belongs in the command, URL, repository, public HTML, browser JavaScript, or an MCP prompt. AccuWeb shared hosting permits at most three scheduled executions per day; for example, use minute 5 and hour */8. Keep the Settings switch off until you are ready to start scheduled work. The protected HTTP and legacy cron routes remain available for compatible tooling and are gated by the same switch.
Governed workflows
PocketPapi adopts the useful operations pattern behind modern enterprise agent platforms: describe work in a bounded task, choose a Site or Local execution lane, use deterministic built-ins for exact checks, route judgment to a configured provider, keep project-scoped memory as candidates until approved, and surface exceptions through the existing review queues. Browser recording, connector discovery, and computer-use sessions require a workstation or a separate automation service; they do not run inside an AccuWeb shared-hosting PHP request.
Simple prompts that work well
For a targeted fix, include the highlighted text and the page URL: “On https://example.com/services, fix the highlighted ‘Book now’ button so it has AA contrast, a visible focus state, and a 44px touch target. Use the existing site MCP/effects integration and apply the change in staging.” For a full connection pass: “Run the MCP sync pack for this site. Check chat, CRM/contact forms, SSO, branding, email identity, Zernio, business network, POS, shop/legal pages, and current visual effects; use existing project knowledge and log every repair.”
Courses, POS, and shared shop offers
Choose course / education in Site Studio to receive the course funnel, course pages, checkout-ready course products, learning materials, and legal/contact page pack. PocketPapi-owned products can be private, shared with selected projects, shared with all projects, or forced as a central promotion. Authorized staff can opt in from pocketpapi-shop.php; referrals are recorded against central orders so bonus status is reviewable.
POS, MyRides, and social operations
Every connected POS installation exposes the same site-scoped /api/control-plane/pos/{action} contract and sitecommander_pos_* MCP tools. It covers the complete suite: catalog/menu and modifiers, orders and line items, payments, register sessions and cash movements, KDS status, inventory events, loyalty, promotions, rewards, gift cards, giveaways, broadcasts, delivery jobs, kiosks, self-serve stations and assistance requests, receipt printers, menu boards, kitchen labels/printables with date-marking presets, settings, reports, and site-scoped email/text subscribers. Social connections and inbox items can be linked to support tickets or POS orders, and social-reply sends the approved reply through the connected provider while recording the ticket/order timeline.
To connect PocketPapi and MyRides, configure a peer on each site with sync-config, then schedule GET /cron/pos-sync?secret=CRON_SECRET in cPanel. The sync is bounded and idempotent. Bearer tokens, passwords, payment credentials, and social-provider secrets are never exported.
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. Public visitors can also use Get updates to choose email or text messages; those public opt-ins remain separate from staff account preferences.
Read the server integration contract →
PocketPapi site connections
Site owners can connect an authorized site to the shared Pocket Papi iOS and Android client from Project Setup. Every project receives Pocket Papi: public sites appear in the mobile chooser, while private sites require a one-time configuration code. Pocket Papi 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.