PIO Team

io.github.PayInOnePublished by GitHub account PayInOnev1.0.0Updated Nov 7, 2026

Read-only, permission-scoped PIO team workflows for payments, payroll and employee onboarding.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote PIO server giving an assistant read-only, permission-scoped access to team workflows for payments, payroll and employee onboarding.

What you can do
  • Read PIO team payment workflows, scoped to the permissions granted to the connected account
  • Read payroll workflows for the team
  • Read employee onboarding workflows
  • No tool list is published, so the exact operations available are not documented in the supplied material
When to use it
Useful when a team already runs payments, payroll or onboarding through PIO and wants an assistant to look up that workflow information without changing it.
Requirements
A remote endpoint at app.pioinc.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
Access is limited to whatever the OAuth account is permitted to see, so review the granted scopes before connecting. The description states the workflows are read-only, but no tool list is published to confirm what each tool does.

Installation

In SourceWeft

  1. Open PIO Team 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.PayInOne%2Fpio/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": {
    "pio-team": {
      "type": "http",
      "url": "https://app.pioinc.com/gateway/foundation/mcp"
    }
  }
}

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.0LatestNov 7, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.