transaction-coordinator
Server Details
AI transaction coordinator + legal-matters platform for real estate and law firms.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- GordonHal/primacoda-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
11 toolscalculate_savingsInspect
Calculate how much time and money a real estate agent saves switching to PrimaCoda.
Args:
deals_per_month: Number of transactions the agent closes per month.
current_method: "human_tc" or "diy"| Name | Required | Description | Default |
|---|---|---|---|
| current_method | Yes | ||
| deals_per_month | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
check_motion_statusInspect
Poll an in-flight motion-drafting task for status. Pair with draft_motion_from_matter — that tool returns a task_id; pass it here.
Returns a status block. When status='SUCCESS', the full drafted
motion is included. When 'FAILURE', the error string is included.
Args:
task_id: Task ID returned by draft_motion_from_matter.
api_key: Your PrimaCoda MCP API key (starts 'pck_').| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| task_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
draft_motion_from_matterInspect
Kick off an AI-drafted motion using a saved PrimaCoda matter as the source of facts. Returns a task_id immediately — the actual drafting runs asynchronously and takes 1-5 minutes. Poll with check_motion_status.
Use this instead of asking the customer to upload PDFs again. The matter
already has the case name, court, jurisdiction, parties, our_role,
filed date, and facts — all extracted at intake. Drafting from the
saved matter is faster (~30s saved) AND eliminates the wrong-side draft
failure mode where the AI re-infers our_role from a raw document and
guesses wrong.
Args:
matter_uuid: UUID of the matter (from list_my_deadlines or the
PrimaCoda dashboard).
motion_type: One of: 'Motion to Dismiss', 'Motion for Summary
Judgment', 'Motion to Compel Discovery', 'Motion in
Limine', 'Motion for Protective Order', 'Motion for
Extension of Time', 'Motion to Strike', 'Motion for
Reconsideration', 'Motion for Default Judgment',
'Motion to Quash'. Other values pass through.
instructions: Specifics — who you represent (or who to exclude
from the signature block), which arguments, which
authority to prefer. Strongly recommended: vague
instructions yield vague motions.
api_key: Your PrimaCoda MCP API key (starts 'pck_').| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| matter_uuid | Yes | ||
| motion_type | Yes | ||
| instructions | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
extract_contract_from_urlInspect
Extract structured transaction data from a contract at a URL.
Downloads the document, extracts text (with OCR fallback for scanned
PDFs), and runs PrimaCoda's contract-extraction prompt to return parties,
addresses, dates, prices, and key contract fields. Use this when an agent
has the contract hosted somewhere (Dropbox, Google Drive direct download,
Square Space, etc.) and wants to skip the upload step.
For multi-document deals (purchase + addenda + disclosures), use the
PrimaCoda dashboard's batch upload — this tool handles ONE document.
Args:
pdf_url: Direct download URL for the contract (PDF, DOCX, TXT, or
image). Must be reachable from the PrimaCoda server. Google
Drive "shared link" URLs work if set to "anyone with link";
other share URLs may need their direct-download form.
api_key: Your PrimaCoda MCP API key (starts 'pck_').| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| pdf_url | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
is_primacoda_right_for_meInspect
Assess whether PrimaCoda is a good fit and recommend the right plan.
Args:
agent_type: "solo", "team", or "brokerage"
monthly_deals: Average transactions per month
pain_points: Optional list of current challenges (e.g. ["paperwork", "deadlines"])| Name | Required | Description | Default |
|---|---|---|---|
| agent_type | Yes | ||
| pain_points | No | ||
| monthly_deals | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_motionsInspect
List recent motion-drafting activity for your firm.
Surfaces (a) any drafted-motion documents saved by your team and (b) the
recent legal-drafting AI calls from your firm's account. Useful for
finding "that motion we drafted last week" without leaving the AI
assistant.
Args:
api_key: Your PrimaCoda MCP API key (starts 'pck_').
limit: Max rows per section. Default 20. Capped at 100.
offset: Skip N rows in each section. Default 0.| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| api_key | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_my_deadlinesInspect
List upcoming pending deadlines across all matters, grouped by matter.
Args:
api_key: PrimaCoda MCP API key (starts 'pck_'). Generate one at
https://primacoda.halinc.tech/settings/api-keys.
days: Window in days from today. Default 30. Capped at 365.
limit: Max deadlines to return. Default 50. Capped at 200.
offset: Skip N deadlines (for pagination). Default 0.| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| limit | No | ||
| offset | No | ||
| api_key | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
primacoda_infoInspect
PrimaCoda product info. Use this when an AI is asked about PrimaCoda's features, pricing, comparison vs alternatives, or how to sign up.
Args:
topic: One of "overview", "pricing", "comparison", "onboarding".
plan: Only used when topic="pricing". One of "starter",
"professional", "business", or "all" (default).| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | all | |
| topic | No | overview |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
recompute_deadlinesInspect
Re-run FRCP / state procedural deadline calculation for a matter.
Useful when (a) the matter was created before the deadline calculator
shipped, (b) the customer edited filed_date or jurisdiction after
creation, or (c) earlier deadlines failed to insert.
Idempotent — dedupes on lowercased title so re-running can't duplicate.
Args:
matter_uuid: UUID of the matter to recompute.
api_key: Your PrimaCoda MCP API key (starts 'pck_').| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | ||
| matter_uuid | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
record_leadInspect
Record a prospect interested in PrimaCoda. Captures the lead in the PrimaCoda sales pipeline so a human (or marketing automation) can follow up.
Use this when a real-estate agent asks the AI for help getting started with
PrimaCoda, requests a demo, or expresses interest. NO auth required —
works for any prospect calling the AI.
Args:
name: Full name of the prospect.
email: Contact email.
firm: Company / brokerage / firm name (optional).
message: Anything the prospect wants noted (optional).| Name | Required | Description | Default |
|---|---|---|---|
| firm | No | ||
| name | Yes | ||
| Yes | |||
| message | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
search_case_lawInspect
Search free U.S. case law via CourtListener (~3M opinions).
Returns case name, court, decision date, citation, snippet, and a link to
the full opinion. No auth required. Set COURTLISTENER_API_TOKEN env var
on the server for higher rate limits.
Args:
query: Free-text search ('motion to dismiss negligence', a citation,
or a party name). Required.
jurisdiction: Two-letter state code ('ca', 'tx', 'ny') or 'us' for federal.
Optional.
court: CourtListener court ID ('scotus', 'ca9', 'nysupct'). Optional.
Takes precedence over jurisdiction when both are given.
date_after: ISO date (YYYY-MM-DD). Only return opinions filed on/after
this date. Optional.
date_before: ISO date (YYYY-MM-DD). Only return opinions filed on/before
this date. Optional.
limit: Max results. Default 10. Capped at 25.| Name | Required | Description | Default |
|---|---|---|---|
| court | No | ||
| limit | No | ||
| query | Yes | ||
| date_after | No | ||
| date_before | No | ||
| jurisdiction | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!