6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Start workflow runs, complete tasks, update form fields and query data sets.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Process Street MCP server connects a Process Street workflow account to Claude, ChatGPT, Microsoft Copilot Studio and any MCP-compatible agent. It exposes 32 tools covering workflow runs, tasks, form fields, approvals, assignments and data sets — so operations teams start runs, chase blocked tasks and query process data in conversation instead of in the Process Street UI.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
openid, profile, email and offline_access. There is no application-level scope to decline at consent time, so a read-only connection is not something you can approve — authorisation comes from your Process Street permissions instead.Every plan. Process Street's MCP documentation lists the feature as available on all plans, with no paid tier gate on the connector itself. The one plan-gated adjacent feature is restricted API keys, which its own help page limits to Enterprise. ChatGPT users need a Pro, Team, Business, Enterprise or Edu subscription on the ChatGPT side.
No. Process Street's MCP documentation states plainly that if SAML SSO is enabled in your organization, the MCP server is not supported at the moment. This is the sharpest prerequisite on the page and it is an organization-level block, not a per-user setting, so SSO-enforced workspaces cannot connect until Process Street ships support.
Only what your own account can. Process Street documents that Admins, Builders and Users can all use the MCP server, and that each can interact solely with resources they already have permission to reach. The connector inherits your existing role and folder, workflow and workflow run permissions rather than granting a separate level of access.
Workflow run deletion is recoverable; data set record deletion is not documented as recoverable. Process Street states that deleted workflow runs can be restored, and only by Admins. Its data set documentation describes no restore path for individual records, and the connector ships no undelete tool for them, so treat record deletion as final.
Not for the standard OAuth connection. Process Street documents the Claude setup as signing in with your own credentials, and Admins, Builders and Users may all use the server. Admin rights matter for two adjacent things: generating an API key for clients without a one-click connector, and restoring any workflow run that was deleted.
With a Process Street API key as a bearer token. Process Street documents adding https://mcp.process.st/ as a remote MCP server and sending an Authorization header carrying the key, with worked configuration examples for VS Code and Cursor. An administrator generates the key from the integrations page in the organization manager.
https://mcp.process.st — an anonymous initialize returnsrobots.txt for www.process.st (HTTP 200, retrieved 2026-08-18). Disallows only /wp-admin/ and carries no Content-Signal directive, so fetching and synthesis are both unrestricted. The host also serves a help-centre llms.txt index at , which is how the two MCP pages above were located. · retrieved 2026-08-18Connect Process Street once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.