Skip to content
Book a demo Start building
1ClickImpact logo

1ClickImpact MCP server

Make a positive environmental impact with every transaction.

1ClickImpact is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the 1ClickImpact integration
Tools
5
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the 1ClickImpact MCP server

Connect 1ClickImpact 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 1ClickImpact and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

1ClickImpact tools your AI can run

Once connected, your assistant can call any of these 1ClickImpact actions by asking in plain language.

  • Capture carbon

    Capture carbon for yourself or on behalf of the customer

    4 fields

  • Clean ocean

    Clean ocean waste yourself or on behalf of the customer

    4 fields

  • Donate Money

    Donate money to support environmental causes

    4 fields

  • Plant Trees

    Plant trees for yourself or on behalf of the customer

    4 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

1ClickImpact MCP, answered.

No. That is the point of it. One Activepieces server exposes 1ClickImpact 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 1ClickImpact 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 5 tools, including Capture carbon, Clean ocean, Donate Money, 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.