# Connect Citation with Gumloop

Let a Gumloop agent work with the documents and sources you authorize.

## Before you connect

Custom MCP connector. Operator setup is required. This is not a published marketplace integration.

Your Citation operator must configure the MCP address and apply the MCP and automation database migrations. Cloud platforms need a reachable HTTPS address. A localhost address works only for software on that computer.

Each token grants access to one workspace for 1 to 90 days. Read permissions are selected initially. Choose writing and exporting only if your workflow needs them. Save credentials in the platform credential store.

- [Download setup package](/api/automation/templates/gumloop)

## Set up Gumloop

1. Create a Citation workspace token with document and source read permissions. Copy the exact MCP address from automation settings. Gumloop requires a reachable HTTPS server.
2. In Gumloop Settings, open Connectors. Use the arrow beside Add Connector and choose Add MCP Connector. Choose Public URL and enter the Citation MCP address, ending in /mcp.
3. Select Bearer authentication and enter the token in Access Token / API Key. Add the connector to a test agent. Ask it to discover tools, list the authorized workspace and read a disposable document.
4. For a write test, create a token with the necessary write scopes and use the included example instructions in a disposable workspace. Verify the returned document ID, saved source and formatted reference in Citation.

This route exposes the twelve existing MCP tools. It does not register a Gumloop event trigger. Bearer authentication is documented by Gumloop; a real account connection is still unverified. The example instructions are a reusable prompt, not a native flow import. OAuth compatibility has not been established for this client.

- [Official Gumloop documentation](https://docs.gumloop.com/nodes/mcp/custom_mcp_servers)

## Supported operations

Find and read documents. Create drafts and save version checked edits. Find, read, add and update sources. Format references, check citation metadata, and export saved text or reference files.

The setup package includes an OpenAPI contract with exact input and output schemas. HTTP actions use POST at the following relative path:

Create draft endpoint
```
/api/automation/v1/actions/create_draft
```

Create draft request
```json
{
  "request_id": "REPLACE_WITH_A_STABLE_UUID",
  "title": "Research intake",
  "text": "Evidence to review."
}
```

Use read_document with include_content before changing a draft. Sending text replaces formatting and citation nodes.

Invoke create_draft through the MCP connector with the same arguments.

## Events and retries

The HTTP event feed reports document creation, document updates, source creation and source updates. Events are saved with the same database transaction as the change. A retried request returns the same event IDs. History is retained for 30 days or 100,000 events per workspace, whichever is smaller.

Use after for ascending pages and before for descending pages. Keep the same workspace, event type and order. Save the final checkpoint only after all pages and downstream actions succeed. A 410 error requires resynchronization. This integration does not send outbound webhooks.

Reuse the same request UUID and exact input after an uncertain save. A 409 error means the version or request input changed. Read and review before making a new request. A 429 response includes a retry interval. Expired or revoked tokens return 401.

## Manage access

Test API access in Citation settings, then test the connection inside your platform. A successful API test confirms Citation access only. Replace a token to invalidate its previous value while keeping its retry history. Update the platform credential before resuming. Revoke the connection to stop access.

- [Automation overview](/docs/automation)