Agent access

Permit News Agent access for Pro and Teams.

Agent access is the remote MCP surface for supported clients that need read-only permit intelligence and report summaries from the same entitlement model used by the customer app. It is in setup readiness and should not be treated as generally available until the launch gate is complete.

Intelligence classification

Permit context a professional team can inspect.

Plan-review correctionsReviewer comments that keep the file from moving forward.Common context
Resubmittal loopsRepeated applicant responses and unresolved review cycles.Common context
Missing documentsIncomplete materials that may require coordination.Common context
Department holdsSpecialty review or routing issues that may need attention.
Routing contextSource activity showing where review responsibility may sit.
Extended reviewLong-running review activity with unclear next movement.

Trust proof

Agent access inherits the same entitlement and legal gates.

The MCP surface is read-only, entitlement checked, and constrained to customer-visible permit intelligence.

Scope

Read-only

Agent access cannot expand market entitlement.

Terms

Legal gate

Current legal acceptance is required.

Output

Redacted

Customer-visible data stays bounded.

Trust surface

Terms, privacy, and source boundaries

Public-source context
No private pipeline claims
Legal acceptance before access

Use the dedicated MCP endpoint.

The canonical remote endpoint is https://mcp.permit.news/mcp. It is separate from the customer app and Admin console so machine access can have distinct auth, rate limits, support logs, and abuse controls.

Remote Streamable HTTP MCP surface

Included context for reviewing this Permit News surface.

OAuth access bound to mcp.permit.news

Included context for reviewing this Permit News surface.

No raw Stripe state or raw OAuth tokens in client-visible claims

Included context for reviewing this Permit News surface.

How it works

Evidence-backed context becomes News items.

  1. 1Monitor public permit-review activityWatch commercial permit activity for review-stage context.
  2. 2Classify permit contextClassify corrections, resubmittals, missing documents, and holds.
  3. 3Package News itemsSummarize evidence, status, review context, and contact path.

Authorization comes from current entitlements.

Stripe bills, Neon projects workspace entitlements, Clerk identifies the signed-in customer, and MCP checks current Neon-derived market access on every request.

Pro and Teams only

Included context for reviewing this Permit News surface.

Plus and one-time Market report buyers do not receive Agent access

Included context for reviewing this Permit News surface.

Payment attention suspends Agent access until billing recovers

Included context for reviewing this Permit News surface.

Classification

Permit context Permit News classifies.

Plan-review correctionsReviewer comments that keep the file from moving forward.
Resubmittal loopsRepeated applicant responses and unresolved review cycles.
Missing documentsIncomplete materials that may require coordination.
Department holdsSpecialty review or routing issues that may need attention.
Routing contextSource activity showing where review responsibility may sit.
Extended reviewLong-running review activity with unclear next movement.

The v1 client matrix is intentionally narrow.

The first supported setup guides target Claude Code, Claude Cowork, and Codex. Each client remains pending live validation until OAuth, consent, revocation, audit, and rate-limit behavior pass production-like QA.

Claude Code

Included context for reviewing this Permit News surface.

Claude Cowork

Included context for reviewing this Permit News surface.

Codex

Included context for reviewing this Permit News surface.

Buyer fit

Teams that can act on permit intelligence.

Permit expeditersPermitting consultantsResidential contractorsArchitectsLendersOwner repsReal estate agentsBusiness development

Connect through OAuth consent in Atelier.

Start from a supported client, point it at https://mcp.permit.news/mcp, sign in through the Atelier consent page, review the requested scopes and entitled markets, accept the current Terms of Service and Privacy Policy when prompted, then approve the grant.

Each user personally accepts the current legal documents

Included context for reviewing this Permit News surface.

Stale acceptance blocks new grants, refreshes, and runtime use

Included context for reviewing this Permit News surface.

Grants can be revoked from Atelier or Admin support

Included context for reviewing this Permit News surface.

Workflow shift

The useful context is timing plus evidence.

Before
  • Referrals
  • Manual portal checks
  • Generic permit lists
  • Emergency outreach
After
  • Filtered News items
  • Review context
  • Evidence trail
  • Reviewable contact path

Data returned through MCP is customer-visible and redacted.

Agent tools expose simplified permit intelligence, redacted evidence summaries, entitled market lists, jurisdiction/filter taxonomies, and report summaries. Report artifact access is signed PDF links only.

No contact-path PII in MCP output

Included context for reviewing this Permit News surface.

No raw public portal payload export

Included context for reviewing this Permit News surface.

No CSV report artifacts

Included context for reviewing this Permit News surface.

Included fields

What the report turns into News

News item listRecent commercial files organized for first-pass review.
Intelligence summariesPlain-language context for why each file deserves review.
Evidence trailsSource context your team can inspect before taking action.
Contact pathsApplicant, architect, owner entity, or other review paths.
Confidence contextA review prompt that helps reject noisy records.
PDF deliveryHuman-readable report package for review and sharing.

FAQ

Common questions

What setup errors should customers expect during preview?

The common failures are unsupported plan, stale legal acceptance, expired or revoked grant, payment attention, cross-market denial, rate limit, and unsupported client behavior.

Is Agent access available on Plus?

No. Agent access is a Pro and Teams surface at launch. Plus customers should upgrade to Pro when they need supported MCP clients.

Can an MCP grant expand market access?

No. A grant can narrow requested access, but every request is checked against current Neon-derived market entitlements.

Can one-time Market report buyers use MCP?

No. One-time Market report purchases grant report access only; they do not include live Agent access.