Process Street

io.github.process-streetPublished by GitHub account process-streetv1.0.0Updated Oct 24, 2026

Connect AI agents to Process Street workflows, tasks, runs, data sets, and operational records.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Hosted Process Street MCP server that lets an AI assistant find, create and manage workflows, runs, tasks, users and data sets in a Process Street account.

What you can do
  • Find and work with workflows, workflow runs, tasks, users and data sets
  • Create and manage workflow runs and assigned tasks
  • Produce reports and summaries from Process Street data
  • Analyze operational records the connected user can access
When to use it
Useful when a team runs recurring operational processes in Process Street and wants an assistant to look up runs and tasks, create or assign work, or summarize process data without leaving the chat client.
Requirements
A remote Streamable HTTP endpoint at mcp.process.st; no local package. Authentication is required: an interactive OAuth authorization flow, or a Process Street API key supplied as a bearer token where the client supports custom authentication. Access follows the connected user's Process Street permissions.
Before you install
The tools can create and manage workflow runs and assigned tasks, so assistant actions change data in the account. Access is limited to the connected user's permissions, and organizations requiring SAML SSO are not supported by the documented connection flow. An API key used as a bearer token is a credential that should be handled carefully.

Installation

In SourceWeft

  1. Open Process Street in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.process-street%2Fprocess-street-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "process-street": {
      "type": "http",
      "url": "https://mcp.process.st/"
    }
  }
}

README

Process Street MCP Server

Process Street's hosted Model Context Protocol server connects compatible AI clients to Process Street workflows, workflow runs, tasks, users, data sets, and operational records.

This repository contains the public discovery metadata for the hosted server. It does not contain the server implementation.

Connect

Use this remote server URL in an MCP client:

text
https://mcp.process.st/

The server uses Streamable HTTP. Compatible clients can use the interactive authorization flow. Process Street API keys can also be supplied as bearer tokens where the client supports custom authentication.

See the Process Street MCP Server guide for setup instructions for supported clients.

Capabilities and access

The server exposes Process Street operations as MCP tools. Depending on the connected user's permissions, these tools can help an AI client:

  • Find and work with workflows, workflow runs, tasks, users, and data sets
  • Create and manage workflow runs and assigned tasks
  • Produce reports and summaries from Process Street data
  • Analyze operational records available to the connected user

Access remains subject to the user's Process Street permissions. Organizations that require SAML SSO are not currently supported by the documented MCP connection flow.

Registry metadata

server.json is published in the Official MCP Registry as io.github.process-street/process-street-mcp version 1.0.0.

Published Registry versions are immutable. Any metadata correction must use a new unique version.

Resources

Repository scope

Issues and pull requests in this repository should concern public discovery metadata or its documentation. Product support and security matters should use the official resources above.

Source: README.md at commit 971e35b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.