6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Mojo — Pocket Capture
Ask an AI agent about your Pocket Capture leads, capture points and funnel.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the Mojo — Pocket Capture connector does
The Pocket Capture MCP server connects a Mojo Systems lead-capture account — QR codes, links and forms used at events, booths and job sites — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 16 tools: fifteen read leads, capture points and funnel metrics, and one stages a draft for you to approve in the app. Sign-in is OAuth.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Mojo — Pocket Capture tools (16)
- capture_point_stats
- capture_velocity
- create_draft
- data_quality
- get_creation_contract
- get_draft
- get_lead
- list_capture_points
- list_drafts
- list_forms
- list_tasks
- plan_for_goal
- search_leads
- setup_health
- unused_capabilities
- who_to_follow_up
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The single advertised scope is narrower than the tool list. Both the server's RFC 9728 descriptor and its authorization server advertise exactly one scope,
mojo.read, on 2026-08-23.create_draftwrites. Either the write is enforced by something other than the scope, or the scope is advertised rather than enforced — advertised scopes are not enforced scopes, and we could not read the dispatch path to tell which. This is the inverse of the usual failure: a scope naming *fewer* verbs than the tools carry, not more. It cannot be read as a guarantee that writes are blocked. - Mojo Systems publishes no tool list. Not one of the 16 names appears in the raw HTML of any page on its site. We can report a vendor *negative* enumeration — an explicit statement of what the connector cannot do — but not a name-by-name diff. The forward direction (directory names absent from the docs) is therefore all 16; the reverse direction (documented names absent from the directory) is empty because there is nothing to compare.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here, and a notify-style parameter on
create_draftcannot be excluded. plan_for_goalandget_creation_contractare unresolved. Neither appears in any vendor document and neither behaviour is settled by its name.- The approval gate is documented, not verified. Mojo Systems states drafts require explicit human approval before going live. That is the connector's central safety property and it lives inside the authenticated app, which we did not enter.
- An agent can fill your drafts list.
create_draftneeds no approval to *stage* a draft. The vendor documents no limit on how many an agent may create. - No rate limit is published. Mojo Systems documents none for the MCP server.
- The directory description is internally garbled. Anthropic's entry reads "every tool touching data tool is read-only" and "It's built write for the operator", both of which look like editing errors in vendor-supplied copy. The intended claims match the connector page; we relied on the connector page.
- This connector was promoted this week. It was listed at
communitytier in our 2026-08-16 snapshot and appears atpartnerin the 2026-08-23 pull. Anthropic states directory verification "is not a security audit". - The underlying platform sends SMS; this connector does not. Mojo Systems' field check-in product dispatches SMS through Twilio. No tool in this listing reaches it, but the capability exists on the account the credential belongs to.
- The marketing site runs a Meta Pixel. Mojo Systems states it does not place advertising pixels on other businesses' capture pages and suppresses the pixel for EU/EEA/UK/Swiss visitors and on the Global Privacy Control signal. Its own policy concedes this may count as "sharing" under California law. Unrelated to the connector, but it is on the page the directory nominates.
Frequently asked questions
What does Pocket Capture actually capture, and from where?
Inbound lead submissions from other people, not anything on your device. Mojo Systems describes a capture point as a QR code or link you display on a sticker, badge or lockscreen; someone else scans it and fills a form. The connector reads what those forms collected. It does not read your screen, clipboard, audio, browser activity or local files.
Can the Pocket Capture connector create or delete anything by itself?
It can stage one thing and delete nothing. Of the 16 tools Anthropic lists, only create_draft carries a write verb, and Mojo Systems states drafts land in the app for you to review and approve before anything goes live. No tool name carries delete, remove, archive, send or update, and the vendor states the AI can never change or delete existing setup.
What OAuth scope does the Pocket Capture MCP server request?
One scope, mojo.read, advertised by both the server's RFC 9728 descriptor and its authorization server on 2026-08-23. That is the rare case of a scope narrower than the tool list, because create_draft writes a draft while the only advertised scope names reading. Treat the mismatch as unresolved rather than as proof the write is blocked.
Is Pocket Capture the same company as Mojo Systems?
Pocket Capture is a product; Mojo Systems LLC is the company that makes it. There is no acquisition or rebrand behind the name difference. Mojo Systems is a Pennsylvania LLC based in Philadelphia that ships two capture products — Pocket Capture for individuals and Capture Hub for teams — which is why the MCP endpoint sits on mojosystems.io.
How long does Mojo Systems keep Pocket Capture lead data?
For the life of the account plus a short grace period. Mojo Systems' privacy policy states lead, contact and check-in data is retained while the Account Holder's account is active, then deleted from active systems and routine backups within ninety days of cancellation. Server logs are kept up to thirty days. No connector tool deletes anything.
Does the Pocket Capture connector expose other people's leads?
No, and Mojo Systems scopes it to one account. The vendor states the connector only ever sees your own captured leads and setup, and its privacy policy describes per-tenant data isolation at the database level. One credential therefore reaches one Account Holder's data, not a shared pool across customers.
Does calling a Pocket Capture tool cost money or credits?
No tool spends anything, and no tool could tell you if it did. None of the 16 names touches billing, credits, quota or usage, and Mojo Systems documents no per-call rate for the connector. Cost sits at the subscription level instead — the connector is gated to Pocket Capture plans that include it.
What personal data enters the agent's context from Pocket Capture?
Contact details written by strangers you met in the field. Mojo Systems' privacy policy states capture forms typically collect name, email, phone, company and a message, and search_leads and get_lead read exactly those records. That free-text message field is attacker-controllable, so treat retrieved lead text as data rather than instructions.
Sources
- Mojo Systems AI Connector page (retrieved 2026-08-23). This is the documentation URL Anthropic's directory nominates.
www.mojosystems.io/robots.txtdisallows ClaudeBot while allowing*; we made one directed read of the vendor-nominated page and did not crawl onward from it. The same file carriesContent-Signal: search=yes, ai-train=no, use=reference— no ai-input signal either way. · retrieved 2026-08-23 - Mojo Systems Pocket Capture product page (retrieved 2026-08-23) · retrieved 2026-08-23
- Mojo Systems homepage, product and pricing tiers (retrieved 2026-08-23) · retrieved 2026-08-23
- Mojo Systems Privacy Policy, retention, subprocessors and capture-form fields (retrieved 2026-08-23, last updated 2026-08-02) · retrieved 2026-08-23
- Mojo Systems Terms of Service, section 16 "Artificial intelligence features" (retrieved 2026-08-23) · retrieved 2026-08-23
- Pocket Capture on the App Store, App Privacy card and in-app purchase tiers (retrieved 2026-08-23) · retrieved 2026-08-23
- Pocket Capture on Google Play, Data safety card (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize returned 401 with
www-authenticate: Bearer resource_metadata=...; RFC 9728 descriptor athttps://mcp.mojosystems.io/.well-known/oauth-protected-resource; authorization server metadata athttps://app.mojosystems.io/.well-known/oauth-authorization-server(2026-08-23). A control path under the same.well-knownprefix returned 401 rather than an interpolated descriptor, so the 200 is genuine. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshots dated 2026-08-16 and 2026-08-23 · retrieved 2026-08-16
- Mojo Systems support — <mailto:build@mojosystems.io> · Privacy
More Productivity connectors
Adobe Experience Manager
Create, edit, publish and delete AEM pages, content fragments and assets from an agent.
Adobe Workfront
Find, create, update and delete Workfront work items from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Mojo — Pocket Capture to work.
Connect Mojo — Pocket Capture once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.