Custom integrations from Connect to Live

Use a signed webhook for one reviewed POST target, Reviewed API for fixed OpenAPI-style operations, or Remote MCP for tools discovered from one fixed Streamable HTTP endpoint. Prefer a native provider action when Codelit already models the service. Common setup asks only for the fixed endpoint, authentication, action, path, risk, and read-only proof; operation IDs, schemas, and runtime limits remain under clearly labeled Expert controls.

1. 1Open the responsible Agent card and add a Custom capability.
2. 2Choose Signed webhook, Reviewed API, or Remote MCP and enter a credential-free fixed HTTPS endpoint.
3. 3Review the safe defaults, add the owner credential, and choose Connect securely. Open an Expert control only when the API contract requires a custom ID, schema, or runtime limit.

Connect stores the encrypted owner credential and normalizes the reviewed definition. Inspect confirms the fixed definition or discovers remote MCP tools. Test checks the credential without a write. Sample runs one read-only operation and returns a transient response preview while retaining only status, attempts, and bounded evidence labels. Make Live pins the reviewed fingerprint and unlocks the action selector.

1. 1Inspect the normalized operations and read or write effects.
2. 2Choose a GET operation or an MCP tool marked read-only, then test the credential.
3. 3Run one read sample and inspect its proof.
4. 4Choose Make Live, then attach one reviewed action to the Agent card.

Codelit supports reviewed tools over a fixed public HTTPS Streamable HTTP endpoint. It pins a negotiated protocol version, bounds pagination and tool schemas, rejects private-network resolution and redirects, and treats all returned content as untrusted data.

• Server-declared readOnly, destructive, and idempotent annotations become conservative Codelit effects and risk.
• Unknown MCP tools default to write and at least medium risk.
• stdio commands, legacy transports, resources, prompts, roots, sampling, server-initiated requests, and arbitrary code remain design-only.
• Imported MCP and OpenAPI workflow definitions do not retain credentials and cannot execute until connected and promoted.

Reviewed API inputs must match the bounded JSON schema. Required fields appear as typed controls, enums become dropdowns, optional fields stay collapsed, and generated presets already satisfy the reviewed schema. Structured values and raw JSON remain available under Expert JSON. String fields may use {{handoff}} to insert prior Agent output without changing the destination, method, or operation. Every hosted write pauses on an exact rendered preview bound to the user, run, tool, operation, input, and expiry.

• Transient read-only requests may retry with the same action identity.
• A dispatched write is attempted once and an uncertain outcome is never replayed automatically, even when the provider ignores idempotency headers.
• Responses are size-capped and framed as untrusted data.
• Receipts retain bounded evidence references, never the owner credential or arbitrary sample response.

Codelit fingerprints the endpoint, auth shape, scopes, runtime policy, reviewed schemas, MCP tools, and MCP server version. A changed local definition, remote MCP capability set, or live response schema pauses the integration until it is inspected, tested, sampled, and promoted again.

1. 1Choose Re-inspect when a live capability changes or a run reports drift.
2. 2Choose Revoke to erase credentials immediately, stop live use, and remove active approvals and workspace grants while retaining the definition for review.
3. 3Choose Delete to erase the definition, grants, samples, and custom-action evidence. Account deletion also removes every credential-owned grant, including grants in another workspace.