Prscnt

Build on Prscnt

Already run your own agency tools — a custom manager portal, a no-code app, an internal agent? Use Prscnt as the orchestration and intelligence layer on top of the stack you already have. Keep your portal, your database, and your connectors. Plug our MCP in next to them.

This page is the quick tour. For the complete, product-agnostic developer documentation — quickstart, auth, composing any stack, the runner, the plugin, a full tool reference, and recipes — see the developer docs.


The model

Prscnt builds zero third-party API clients and stores zero third-party credentials. When work needs to touch your tools, Prscnt returns a proposed structure (a Drive folder tree, a calendar event, an invoice payload) and your agent drives your connector to execute it. Prscnt holds only thin pointers back to your records (a Prscnt deal linked to a record id + URL in your system) plus its own proprietary intelligence: rate corpus, brand reliability, partnership graph, creator-brand fit, voice profiles, deal pipeline, contract playbooks, invoicing/AR, and content analysis. Your customer data and credentials never leave your stack.

One thing to know up front. There is no plain-REST endpoint. Every Prscnt tool is reached only through an MCP client with an LLM in the loop (JSON-RPC at POST https://mcp.prscnt.com/v1/mcp). A raw Softr button or Airtable automation can't call Prscnt directly — the pattern is always your portal → a small LLM agent runner (holding the Prscnt MCP + your own connectors) → writes results back into your data.

Integration postures

a. In-Claude composition — fastest, zero code

When: your managers already work in Claude day to day. How: each manager connects their own stack MCPs (Gmail, Drive, QuickBooks, Apollo, Airtable, Monday, HubSpot) plus the Prscnt MCP in the same session. Claude selects tools across all of them in one conversation — pull a rate with rate_benchmark, draft with voice_draft, create the Gmail draft via the manager's own Gmail connector. Zero code; the human approves every outbound action.

b. Custom portal + agent backend — the headline case

When: you run a custom manager portal (e.g. Softr on Airtable, a no-code app, or an internal agent) and want Prscnt as the brain behind it.

Softr UI    managers click "Quote this deal", "Vet brand", "Draft outreach"
   |  (row state, button triggers)
Airtable    Deals, Contacts, Brands, Partnerships, Payments tables
   |  read row   ^ write results back
Orchestration agent  =  LLM runner + Prscnt MCP + Airtable MCP
                        (+ Gmail / QuickBooks / Apollo MCPs)

The agent reads an Airtable row, calls Prscnt tools, and writes results back into Airtable so they surface in Softr. Per stage:

You build the Softr UI, the Airtable schema, and the agent runner glue. You get all intel, pipeline, voice, invoicing, and contract logic for free.

Start from the template. You don't have to write the runner from scratch. The complete orchestration-runner template is in the docs — five short files you copy into your own project: a webhook server (POST /run) wired to the Prscnt MCP, with slots for your own connectors and a built-in human-approval gate. Point your Softr button or Airtable automation at it and you're orchestrating. For the full skill and subagent set, install the prscnt plugin (claude plugin add) and load it via the Agent SDK plugins option — same brain, maintained by us, no rebuild on your side.

c. Programmatic / headless

No REST API or webhook returns intel JSON. To trigger Prscnt from your portal without a human in chat, stand up a small LLM agent runner (e.g. an Agent SDK process) that your Softr button or Airtable automation pings via your own webhook. That runner holds the Prscnt MCP connection + a bearer token, takes a row id, runs the sequence above, and writes back to Airtable. (You can hand-roll a raw JSON-RPC client — initialize → read Mcp-Session-Idtools/call — but then you own all tool selection; treat as advanced.) Either way it consumes your workspace's tier rate limit and monthly allowances.

d. Event recipes

When the portal knows an event happened ("deal signed", "invoice overdue") and wants the next-best action sequence: workflow_describe lists definitions; workflow_propose returns proposed actions for user approval (never auto-fired); orchestration_recipes returns cross-tool recipe cards. Your agent surfaces the proposed steps in your portal and executes only what a manager approves.


Which Prscnt tool for which job

JobTool(s)Type
Price a dealrate_benchmark, deals_benchmark, comparator_pay_historyread
Vet a brand's reliabilitybrand_reliability, brand_fingerprint, negotiation_intelread
Pick the right creatorroster_match_brand, creator_brand_fit, check_exclusivity_conflictread
Draft outreach in-voicevoice_draft, voice_classify_replyread
Advance a dealdeals_update_stage, deals_bulk_createwrite
Invoice + chase paymentinvoice_prepare, invoice_record_qbo, invoice_payment_reconcile, ar_statusmixed
Redline a contractcontracts_run_playbook, contracts_get_playbook, contracts_set_playbookmixed
Source new brandsactive_spenders, competitive_landscape, brand_spend, sourcing_filter_newread
Sync a deal to your CRM / Airtable / Mondaycrm_import, stack_link_deal, stack_resolve_deal, stack_deal_refsmixed

Setup

1. Connect the Prscnt MCP

Add an HTTP MCP server in your client (Streamable HTTP, JSON responses):

{"mcpServers":{"prscnt":{"type":"http",
  "url":"https://mcp.prscnt.com/v1/mcp",
  "headers":{"Authorization":"Bearer <token>"}}}}

The bearer is either a Clerk OAuth token (claude.ai Add custom connector → Authorize) or a static prscnt_live_ / sk_live_ API key minted from the seat path once you're connected. First Authorize auto-provisions a free workspace — connect here.

2. Connect your own stack MCPs

Airtable and Monday are first-class bring-your-stack connectors alongside HubSpot, Asana, Notion, and DocuSign — plus Gmail, Drive, Calendar, QuickBooks, and Apollo as needed. Prscnt's check_integrations / connect_qbo / connect_apollo give guidance only; they store no credentials.

3. Run the link-then-mirror loop

crm_import pulls your brand-contact graph into Prscnt read-only → stack_link_deal points each Prscnt deal at its record in your system (id + URL only) → stack_resolve_deal for the reverse lookup. Both systems point at each other; Prscnt never copies your data.


Guardrails


Questions or want a hand wiring your portal: support@prscnt.com. See also the general docs.