Jitsu MCP Server: Setup for Claude, Cursor and More

• Lists the workspaces you can use

  Lists every Jitsu workspace your account can open.

  Try: “Which Jitsu workspaces do I have?”

  Read · list_workspaces

• Lists items of one type in a workspace

  Lists destinations, streams, services, functions, connections, domains, custom images or notifications in a workspace.

  Try: “List all destinations in my main workspace.”

  Read · list_resources

• Shows one item by id

  Returns the full settings of a single resource by its id.

  Try: “Show me the settings of the BigQuery destination.”

  Read · get_resource

• Shows which fields a resource type needs

  Returns the JSON Schema for creating or updating a resource type, so the assistant knows the exact fields before it writes.

  Try: “What fields does a webhook destination need?”

  Read · get_resource_schema

• Creates a new item

  Creates a new destination, stream, function, connection or other resource. Repeating the call creates another one.

  Try: “Create a stream called web-prod.”

  Write · create_resource

• Changes an existing item

  Overwrites an existing resource by id. The tool is flagged as destructive because it replaces the old settings.

  Try: “Change the destination timeout to 30 seconds.”

  Write · update_resource

• Deletes an item

  Deletes a resource by id. Jitsu flags this as destructive.

  Try: “Delete the old test destination.”

  Delete · delete_resource

• Lists where you can read events from

  Lists the streams, connections and destinations you can read Live Events for.

  Try: “Which sources can I read events from?”

  Read · list_event_sources

• Reads recent live events and logs

  Reads recent Live Events: incoming events, function logs, warehouse write statuses and the dead-letter queue, with filters for source, level, time and text.

  Try: “Show errors from the last hour on the web-prod stream.”

  Read · query_events

• Starts a data sync

  Starts a sync run for a service, and can start a full re-sync. Each call starts another run.

  Try: “Run a full re-sync of the Stripe service.”

  Write · run_sync

• Stops a running sync

  Cancels a sync task that is running.

  Try: “Cancel the sync that is running now.”

  Write · cancel_sync

• Lists recent sync runs

  Lists recent sync tasks, filterable by sync, status and time range.

  Try: “Show failed syncs from this week.”

  Read · list_sync_tasks

• Reads the change history

  Reads the audit log of configuration changes, membership changes and logins. Workspace owners can read one workspace and platform admins can read all of them.

  Try: “What did the MCP change in this workspace today?”

  Read · get_audit_log

• Shows the log of a sync run

  Returns the log records of one sync task.

  Try: “Show the logs for the last failed sync.”

  Read · get_sync_logs

• Shows what a connector needs

  Returns the JSON schema of the credentials a connector package needs. The first call starts the work and the assistant polls for the result.

  Try: “What credentials does the Postgres connector need?”

  Network · get_connector_spec

• Lists what a connector can sync

  Asks a connector which streams it can sync. It contacts the source system and the assistant polls for the result.

  Try: “Which tables can I sync from this Postgres service?”

  Network · discover_streams

• Tests a service's saved credentials

  Starts a check of a service's stored credentials against the real source.

  Try: “Check that the Stripe credentials still work.”

  Network · check_source_credentials

• Returns the result of a credentials check

  Returns the outcome of the credentials check started earlier.

  Try: “What was the result of the credentials check?”

  Read · get_source_check_result

• Shows a sync's saved cursor

  Returns the saved incremental cursor of a sync, by stream.

  Try: “Show the saved sync state for the orders stream.”

  Read · get_sync_state

• Clears a sync's saved cursor

  Deletes the saved cursor for one stream or all streams, so the next run syncs everything from scratch. Jitsu flags it as destructive.

  Try: “Reset the sync state for the orders stream.”

  Delete · reset_sync_state

• Tests destination credentials

  Tests the credentials of an existing destination, or of one you have not saved yet.

  Try: “Test the credentials for the Snowflake destination.”

  Network · test_connection

• Tries a function on a sample event

  Runs a function against a sample event and returns the result, logs and store changes. Nothing is saved, but the function code can call outside systems.

  Try: “Run my enrich function on this sample event.”

  Runs code · run_function

• Tries a profile-builder function on sample events

  Runs a profile-builder function against sample events. Nothing is saved.

  Try: “Test the profile builder on these three events.”

  Runs code · run_profile_builder

• Shows event counts

  Returns event counts per period, connection, stream, destination and status.

  Try: “How many events failed per destination yesterday?”

  Read · get_event_stat

• Shows which syncs worked

  Lists distinct source to destination pairs that had at least one successful sync in a period.

  Try: “Which source and destination pairs synced this week?”

  Read · get_sync_stat

• Shows profile-builder progress

  Returns the build progress of a profile-builder version.

  Try: “How far along is the latest profile builder?”

  Read · get_profile_builder_stats

Watch out for

• It can delete resources and reset sync state

  delete_resource, update_resource and reset_sync_state are flagged destructive. Your assistant should ask before running them. github.com

• An API key does everything you can

  For CI, Jitsu says the personal key inherits your workspace access. Use OAuth sign-in for interactive work and revoke keys you no longer need. jitsu.com

• Function tests can run code that reaches outside

  run_function runs user function code, which may call other systems. Test with sample events you are comfortable sending. github.com

• Changes are logged with an MCP origin

  Every change lands in the workspace audit log. Review it after an assistant session. jitsu.com

Security advisories