OpenMandate

Official15 toolsLive

by openmandate

OpenMandate is in private development and is not accepting new mandates or integrations.

ai.openmandate/mcp MCP Server

The ai.openmandate/mcp Model Context Protocol (MCP) server is associated with OpenMandate. The provided description states that OpenMandate is in private development and is not accepting new mandates or integrations. The server is listed with 15 tools.

🛠️ Key Features

MCP server for OpenMandate
15 available tools

🚀 Use Cases

Not specified in the provided data

⚡ Developer Benefits

Tool availability count is provided (15)

⚠️ Limitations

OpenMandate is in private development
Not accepting new mandates or integrations

Captured live from the server via tools/list.

openmandate_create_mandate

Create a new mandate on OpenMandate. Provide what the user is looking for (want) and what they bring to the table (offer). The user's verified contacts are automatically attached. Returns the mandate with follow-up questions. You MUST relay these questions to the user and collect their actual answers before calling openmandate_submit_answers. Do not answer questions on the user's behalf. If the user has no verified contacts, they must add one first at https://openmandate.ai/settings or use openmandate_list_contacts to check.

Parameters2

want	string	required	What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters.
offer	string	required	What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters.

Raw schema

{
  "type": "object",
  "properties": {
    "want": {
      "type": "string",
      "description": "What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters."
    },
    "offer": {
      "type": "string",
      "description": "What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters."
    }
  },
  "required": [
    "want",
    "offer"
  ]
}

openmandate_submit_answers

Submit the user's answers to pending intake questions. The mandate must be in 'intake' status with pending questions. IMPORTANT: Before calling this, you must show each pending question to the user and collect their real answer. Never fabricate or infer answers. OpenMandate may return additional questions. Relay each round to the user until the mandate becomes active.

Parameters2

mandate_id	string	required	The mandate ID to submit answers for.
answers	array	required	Array of answers to pending questions.

Raw schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to submit answers for."
    },
    "answers": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "question_id": {
            "type": "string",
            "description": "Question ID from pending_questions."
          },
          "value": {
            "type": "string",
            "description": "Answer value. For text: your answer string. For single_select: the option value. For multi_select: comma-separated option values (e.g. 'python, go')."
          }
        },
        "required": [
          "question_id",
          "value"
        ]
      },
      "description": "Array of answers to pending questions."
    }
  },
  "required": [
    "mandate_id",
    "answers"
  ]
}

openmandate_get_mandate

Get a mandate by ID. Returns the mandate's current status, any pending intake questions, and summary once active. Use this to check progress or retrieve questions after creating a mandate.

Parameters1

mandate_id

string

required

The mandate ID to retrieve.

Raw schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to retrieve."
    }
  },
  "required": [
    "mandate_id"
  ]
}

openmandate_list_mandates

List the user's open mandates. Returns non-closed mandates by default. Pass status to filter (e.g. status='closed' for history).

Parameters2

status	string	optional	Filter by status: intake, active, matched, pending_input, closed.
limit	integer	optional	Maximum number of mandates to return (default 20, max 100).

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by status: intake, active, matched, pending_input, closed.",
      "enum": [
        "intake",
        "active",
        "matched",
        "pending_input",
        "closed"
      ]
    },
    "limit": {
      "type": "integer",
      "description": "Maximum number of mandates to return (default 20, max 100).",
      "default": 20
    }
  },
  "required": []
}

openmandate_close_mandate

Close (withdraw) a mandate. This is permanent — the mandate will stop matching and cannot be reopened. Only close if the user explicitly wants to withdraw.

Parameters1

mandate_id

string

required

The mandate ID to close.

Raw schema

{
  "type": "object",
  "properties": {
    "mandate_id": {
      "type": "string",
      "description": "The mandate ID to close."
    }
  },
  "required": [
    "mandate_id"
  ]
}

openmandate_list_matches

List matches for the authenticated user. Returns matches with compatibility grade, strengths, and concerns. Check this periodically after a mandate becomes active.

Parameters1

limit

integer

optional

Maximum number of matches to return (default 20, max 100).

Raw schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Maximum number of matches to return (default 20, max 100).",
      "default": 20
    }
  },
  "required": []
}

openmandate_get_match

Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.

Parameters1

match_id

string

required

The match ID to retrieve.

Raw schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to retrieve."
    }
  },
  "required": [
    "match_id"
  ]
}

openmandate_respond_to_match

Accept or decline a match. If you accept and the other party also accepts, contact info is revealed to both sides. Declining is permanent for this match.

Parameters4

match_id	string	required	The match ID to respond to.
action	string	required	Either 'accept' or 'decline'.
decline_reason	string	optional	Why the user is declining. Only used when action is 'decline'.
decline_reason_text	string	optional	Free-text detail when decline_reason is 'other'.

Raw schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to respond to."
    },
    "action": {
      "type": "string",
      "description": "Either 'accept' or 'decline'.",
      "enum": [
        "accept",
        "decline"
      ]
    },
    "decline_reason": {
      "type": "string",
      "description": "Why the user is declining. Only used when action is 'decline'.",
      "enum": [
        "wrong_skills",
        "stage_mismatch",
        "location",
        "not_enough_info",
        "already_found",
        "other"
      ]
    },
    "decline_reason_text": {
      "type": "string",
      "description": "Free-text detail when decline_reason is 'other'."
    }
  },
  "required": [
    "match_id",
    "action"
  ]
}

openmandate_submit_outcome

Report how a confirmed match went. Available after both parties accepted and contact info was revealed. Outcomes: - 'succeeded': Found the right person. Mandate closes. - 'failed': Didn't work out. Mandate reactivates for new matches. - 'ongoing': Still in conversation. OpenMandate checks back later. IMPORTANT: Always confirm the outcome with the user before submitting. This affects their mandate and matching status.

Parameters2

match_id	string	required	The match ID to report outcome for.
outcome	string	required	Match outcome.

Raw schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "description": "The match ID to report outcome for."
    },
    "outcome": {
      "type": "string",
      "description": "Match outcome.",
      "enum": [
        "succeeded",
        "ongoing",
        "failed"
      ]
    }
  },
  "required": [
    "match_id",
    "outcome"
  ]
}

openmandate_list_contacts

List the user's verified contacts. These are the contacts revealed to the other party on match confirmation. Each contact has an ID, type, display label, and verification status.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

openmandate_add_contact

Add a new contact for the user. A verification code (OTP) will be sent to the contact address. The user must verify the contact using openmandate_verify_contact before it can be used on mandates. The first contact added becomes the primary contact automatically.

Parameters3

contact_type	string	required	Contact type.
contact_value	string	required	The contact address to add (e.g. email address).
display_label	string	optional	Optional human-readable label (e.g. 'Work email'). Defaults to the contact type.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_type": {
      "type": "string",
      "description": "Contact type.",
      "enum": [
        "email"
      ]
    },
    "contact_value": {
      "type": "string",
      "description": "The contact address to add (e.g. email address)."
    },
    "display_label": {
      "type": "string",
      "description": "Optional human-readable label (e.g. 'Work email'). Defaults to the contact type."
    }
  },
  "required": [
    "contact_type",
    "contact_value"
  ]
}

openmandate_verify_contact

Verify a contact by submitting the OTP code sent to it. The user must check their email for the 8-digit code. After verification, the contact can be used on mandates.

Parameters2

contact_id	string	required	The contact ID to verify.
code	string	required	The 8-digit verification code from the email.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to verify."
    },
    "code": {
      "type": "string",
      "description": "The 8-digit verification code from the email."
    }
  },
  "required": [
    "contact_id",
    "code"
  ]
}

openmandate_update_contact

Update a contact's display label or set it as the primary contact. Setting a contact as primary will unset any other primary contact.

Parameters3

contact_id	string	required	The contact ID to update.
display_label	string	optional	New display label for the contact.
is_primary	boolean	optional	Set to true to make this the primary contact.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to update."
    },
    "display_label": {
      "type": "string",
      "description": "New display label for the contact."
    },
    "is_primary": {
      "type": "boolean",
      "description": "Set to true to make this the primary contact."
    }
  },
  "required": [
    "contact_id"
  ]
}

openmandate_delete_contact

Delete a contact. If the deleted contact was primary, the next verified contact is automatically promoted. This is permanent.

Parameters1

contact_id

string

required

The contact ID to delete.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to delete."
    }
  },
  "required": [
    "contact_id"
  ]
}

openmandate_resend_otp

Resend the verification code for a pending contact. Use this if the user didn't receive the code or it expired (codes expire after 10 minutes). Rate limited to 3 per contact per hour.

Parameters1

contact_id

string

required

The contact ID to resend verification for.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_id": {
      "type": "string",
      "description": "The contact ID to resend verification for."
    }
  },
  "required": [
    "contact_id"
  ]
}

Install

Tools (15)

openmandate_create_mandateopenmandate_submit_answersopenmandate_get_mandateopenmandate_list_mandatesopenmandate_close_mandateopenmandate_list_matchesopenmandate_get_matchopenmandate_respond_to_match

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.openmandate.ai/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.openmandate.ai/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

ai.openmandate/mcp MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

openmandate_create_mandate

openmandate_submit_answers

openmandate_get_mandate

openmandate_list_mandates

openmandate_close_mandate

openmandate_list_matches

openmandate_get_match

openmandate_respond_to_match

openmandate_submit_outcome

openmandate_list_contacts

openmandate_add_contact

openmandate_verify_contact

openmandate_update_contact

openmandate_delete_contact

openmandate_resend_otp

Install

Remote endpoint

Related servers