Read a selected inbox and contact book. Prepare customer handoffs with original conversation IDs using your personal Missive access.
Example workflows
Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.
Prepare an inbox handoff
Read one page of 20 conversations from my Missive inbox with inbox true. Prepare a handoff table with each conversation ID, latest subject, assignee and last activity where returned. Identify questions that need the original message body; do not infer their answers from the subject alone. Do not send messages, close conversations or fetch more pages.
Explore this command: missive.conversations.list
Find customer contacts
First ask me for the Missive contact book to use, or find it with the contact-books command. Read one page of 20 contacts using that contact_book ID and offset 0. Return names, organization and contact IDs where available so I can match the right customer to a conversation. Do not enrich contacts from other services or change their records.
Explore this command: missive.contacts.list
What you can do (4)
What you can do
Available commands: 4 (4 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Find Missive contact books — missive.contact-books.list |
Read |
Read contacts from a selected Missive contact book — missive.contacts.list |
Read |
Read the Missive inbox for a customer handoff — missive.conversations.list |
Read |
Read a selected Missive conversation — missive.conversations.get |
Read |
Connect and use
This connection uses your provider account.
Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.
Get your provider credentials
Follow these steps for Missive, then enter the issued values in the connection form below.
- Requires a Missive Productive plan. In Missive, open Preferences → API and create a dedicated personal token. Its access follows your user permissions. Start by finding a contact book, then pass its ID to read contacts. Inbox reads use one page; pass the last_activity_at of the oldest result as until to continue. No messages are sent and no inbox state is changed. Revoke the token in Missive when finished.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Missive personal API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"limit": 20,
"offset": 0
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Find Missive contact books — missive.contact-books.list
Find Missive contact books. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.limit |
integer | Optional | minimum: 1; maximum: 200 |
|
query.offset |
integer | Optional | minimum: 0; maximum: 1000000 |
Full JSON Schema
Example input
{
"query": {
"limit": 20,
"offset": 0
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read contacts from a selected Missive contact book — missive.contacts.list
Read contacts from a selected Missive contact book. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.contact_book |
string | Required | minLength: 1; maxLength: 512 |
|
query.limit |
integer | Optional | minimum: 1; maximum: 200 |
|
query.offset |
integer | Optional | minimum: 0; maximum: 1000000 |
|
query.search |
string | Optional | minLength: 1; maxLength: 200 |
Full JSON Schema
Example input
{
"query": {
"contact_book": "book-1",
"limit": 20,
"offset": 0
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read the Missive inbox for a customer handoff — missive.conversations.list
Read the Missive inbox for a customer handoff. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.inbox |
boolean | Required | const: true |
|
query.limit |
integer | Optional | minimum: 1; maximum: 50 |
|
query.until |
integer | Optional | minimum: 0; maximum: 4102444800 |
Full JSON Schema
Example input
{
"query": {
"inbox": true,
"limit": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a selected Missive conversation — missive.conversations.get
Read a selected Missive conversation. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.conversation_id |
string | Required | minLength: 1; maxLength: 512 |
Full JSON Schema
Example input
{
"path": {
"conversation_id": "conversation-1"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.