Skip to content
HTTP (OAuth2) logo

HTTP (OAuth2) MCP server

Give your AI assistant 1 tool it can call in HTTP (OAuth2), over one server URL.

HTTP (OAuth2) is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
1
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
September 2026

About the HTTP (OAuth2) MCP server

Connect HTTP (OAuth2) once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches HTTP (OAuth2) and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

HTTP (OAuth2) tools your AI can run

Once connected, your assistant can call any of these HTTP (OAuth2) actions by asking in plain language.

  • Send an OAuth2 Request

    Sends HTTP request to a specified URL that requires OAuth 2.0 authorization and returns the response.

    10 fields

Give your assistant HTTP (OAuth2)

Connect HTTP (OAuth2) once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

HTTP (OAuth2) MCP, answered.

No. That is the point of it. One Activepieces server exposes HTTP (OAuth2) alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect HTTP (OAuth2) in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Send an OAuth2 Request, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.