Permio

io.github.perms-ioPublished by GitHub account perms-iov1.0.0Updated Nov 5, 2026

Check and manage RBAC permissions, roles, groups and grants in a Permio (perms.io) project.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote Permio MCP server that lets an assistant check and manage RBAC permissions, roles, groups and grants in a Permio project.

What you can do
  • Check and read permissions, roles, groups and grants in a Permio project.
  • Manage those RBAC objects, such as creating or changing roles, groups and grants, when a full-access key is used.
  • Scope each call to one project through the project header.
When to use it
Useful when an assistant needs to inspect or administer access control in a Permio project, for example auditing who can do what or adjusting roles and grants during development or operations work.
Requirements
A remote streamable HTTP endpoint at mcp.perms.io; no local package. A Permio API key sent as the Authorization header in the form Bearer perms_..., created in the Permio dashboard. The X-Permio-Project header naming the project, which must be the API key's own project.
Before you install
The API key is a secret passed in the Authorization header; a full-access key can make changes, while a check-only key is limited to checking and reading. Changes to roles, groups and grants alter access control, so review them before applying. The project header must match the key's project.

Installation

In SourceWeft

  1. Open Permio in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.perms-io%2Fpermio/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.

{
  "mcpServers": {
    "permio": {
      "type": "http",
      "url": "https://mcp.perms.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 5, 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.