Create a connector from the catalog
create_connectorCreate an organization connector from a Valet catalog entry. It is the step after list_catalog_connectors found the entry for the product the user named; attach_connector then lets a website's pages call it.
An entry that needs no key, or whose keys the organization already holds as secrets, is created at once. An entry that needs a key from a person is not created here. Give reason, saying plainly why it is needed. The answer carries a request whose url the person opens, signed in to Valet, to enter each key; the connector is created when they complete it, and its name is in the answer now. Give the person the url, then follow the request with get_request. Never ask the person to type a key into this conversation. Optional keys are not asked for; the person can add them on the dashboard's Integrations page.
An entry that authorizes in a browser, OAuth or a Composio toolkit, makes a request the same way: the person opens its url, signs in to the provider from there, and the connector is created under the name in the answer. An entry the organization already has is refused, naming list_connectors; no second connector is made. Returns the connector's name, the catalog entry it came from, the slots filled from secrets the organization already held, whether a website can hold it, and the request when a person must enter keys or sign in. Requires connecting a Valet account.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"entry": "<entry>"
},
"name": "create_connector"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entry | Yes | Which catalog connector to add to the organization, named as list_catalog_connectors lists it. | |
| reason | No | Shown to the person on the request page to explain why the values are needed, so they can decide whether to enter them, such as: The agent reads Linear tickets and needs your Linear sign-in. | |
| org_name | No | The Valet organization to create the connector in. Omit to use the organization the account joined first. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| org | Yes | Name of the Valet organization the call acted in. | |
| entry | Yes | The catalog entry the connector came from, in the catalog's own spelling. | |
| request | No | The request a person completes in the dashboard to enter a value that must not pass through this conversation. Absent when nothing needs a person. | |
| secrets | No | Names of the secret slots filled from secrets the organization already held. Names only, never values. Absent when none were filled. | |
| connector | Yes | The connector's name, which attach_connector takes. While request is set the connector does not exist yet; it takes this name when the person completes the request. | |
| site_compatible | Yes | True when a website can hold this connector once it is created: an HTTP MCP server. False means only agents can attach it. |