Portaur account

com.portaurPublished by portaur.comOfficial publisherv1.0.0Updated Oct 31, 2026

A Portaur customer's own proposals, contracts, billing and support requests. Sign-in required.

The publisher's own server: Portaur

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote Portaur endpoint that lets an assistant work with a signed-in customer's own proposals, contracts, billing and support requests.

What you can do
  • Access the customer's own proposals and contracts
  • Review billing information
  • Look up and handle support requests
  • All actions run against the signed-in Portaur account through a hosted remote endpoint; no tool list is published, so exact operations are not documented.
When to use it
Useful when a Portaur customer wants an assistant to help review or manage their own proposals, contracts, billing and support requests without leaving the conversation.
Requirements
A remote MCP endpoint at portaur.com reached over streamable HTTP, plus OAuth sign-in with a Portaur account. No environment variables or headers are declared.
Before you install
The server exposes a customer's business records, including contracts and billing, to the connected assistant; access is tied to the OAuth sign-in, so review what the assistant may read or change and sign out or revoke access when no longer needed.

Installation

In SourceWeft

  1. Open Portaur account 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/com.portaur%2Fportaur-account/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": {
    "portaur-account": {
      "type": "http",
      "url": "https://portaur.com/mcp/account"
    }
  }
}

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

Score

83% 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
  • 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.

Other Portaur integrations