mcpbeat Sign in

Raisely MCP Server

by usefulapi Your server? Claim it
answering

Raisely is answering right now. Last checked 15 min ago. It exposes 23 tools. Last commit 1 Sep 2026.

Read campaigns, donations, profiles and supporters; record offline donations and upsert users.

Uptime history 47 days of history · worst day 13%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
23
Tools
read from the server
179 ms
Response time
average over 24h
0
Stars
last commit 1 Sep 2026

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims local-only, but ships network tools raisely_request 
заявлено «локально, без передачи данных», но есть raisely_request

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Raisely and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add raisely --transport http https://raisely.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "raisely": {
      "url": "https://raisely.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.raisely]
url = "https://raisely.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "raisely": {
      "url": "https://raisely.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "raisely": {
      "url": "https://raisely.usefulapi.io/mcp"
    }
  }
}

Available tools 23

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

campaign
get_campaign
Fetch a single campaign by id or path/slug. Raisely API: GET /campaigns/{campaign}. Returns { data:{...} }.
list_campaign_donations
Convenience: list donations for a specific campaign. Raisely API: GET /campaigns/{campaign}/donations. Returns { data:[...], pagination }.
list_campaign_profiles
Convenience: list fundraising profiles for a specific campaign. Raisely API: GET /campaigns/{campaign}/profiles. Returns { data:[...], pagination }.
donation
create_donation
MUTATES Raisely data: records a donation (use for OFFLINE/manual donations — e.g. cash or cheque). Raisely API: POST /donations with the body wrapped as { data: {...} }. Required by the API: amount (integer, in cents/smallest currency unit), currency (3-letter code), email (donor), type (ONLINE or OFFLINE), method (payment gateway, e.g. OFFLINE). Link it to a campaign/profile via campaignUuid/profileUuid. Everything else (firstName, lastName, message, date, items, public, private, ...) goes through `fields`. Returns the created donation.
get_donation
Fetch a single donation by uuid. Raisely API: GET /donations/{uuid}. Returns { data:{...} }.
profile
get_profile
Fetch a single fundraising profile by path (a URL slug OR the uuid — a string either way). Raisely API: GET /profiles/{path}. Returns { data:{...} }.
update_profile
MUTATES Raisely data: updates a fundraising profile's goal/name/story. Raisely API: PATCH /profiles/{path} with the body wrapped as { data: {...} } (only included fields change). Use `fields` for goal, name, description/story, public, private, and any other documented field. Set overwriteCustomFields:true to overwrite (rather than preserve) unspecified custom fields. The path is never sent in the body.
user
get_user
Fetch a single user (donor/supporter) by uuid. Raisely API: GET /users/{uuid}. Returns { data:{...} }.
list_user_donations
Convenience: a donor's giving history. Raisely API: GET /users/{uuid}/donations. Returns { data:[...], pagination }.
authenticated
get_authenticated_user
Verify credentials and show the currently authenticated user plus their privileges. Raisely API: GET /authenticate. Use this first to confirm RAISELY_API_KEY works. Returns { data:{...} }.
campaigns
list_campaigns
List fundraising campaigns. Raisely API: GET /campaigns. Returns the list envelope { data:[...], pagination }.
donations
list_donations
List donations. Raisely API: GET /donations. Filter via `params` (e.g. campaign, status, sort, order). Returns { data:[...], pagination }.
orders
list_orders
List orders (ticket/product purchases). Raisely API: GET /orders. Filter via `params`. Returns { data:[...], pagination }.
post
create_post
MUTATES Raisely data: publishes a post (a campaign/profile update). Raisely API: POST /posts with the body wrapped as { data: {...} }. Required by the API: path (the post's URL slug), body (the content), photoUrl. Link it to a profile via profileUuid (pass through `fields`). Extra fields (title, date, ...) via `fields`. Returns the created post.
posts
list_posts
List posts (campaign/profile updates). Raisely API: GET /posts. Filter via `params`. Returns { data:[...], pagination }.
profiles
list_profiles
List fundraising profiles (individual/team fundraising pages). Raisely API: GET /profiles. Filter via `params` (e.g. campaign, type, sort, order). Returns { data:[...], pagination }.
raisely
raisely_request
Power-user escape hatch: GET any Raisely API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the base, starting with a slash, INCLUDING any query string, e.g. "/subscriptions/{uuid}/donations" or "/donations?limit=50". Returns the parsed JSON.
segments
list_segments
List saved audience segments. Raisely API: GET /segments. Returns { data:[...], pagination }.
subscription
get_subscription
Fetch a single subscription (recurring donation) by uuid. Raisely API: GET /subscriptions/{uuid}. Returns { data:{...} }.
subscriptions
list_subscriptions
List subscriptions (recurring donations). Raisely API: GET /subscriptions. Filter via `params`. Returns { data:[...], pagination }.
tags
list_tags
List tags used to label records. Raisely API: GET /tags. Returns { data:[...], pagination }.
upsert
upsert_user
MUTATES Raisely data: creates OR updates a supporter/donor, matched by email (safer than a plain create — no duplicates). Raisely API: POST /users/upsert with the body wrapped as { data: {...} }. Typed: email (the match key), firstName, lastName; everything else (phoneNumber, address, public, private, ...) via `fields`. Returns the upserted user.
users
list_users
List users (donors/supporters/fundraisers). Raisely API: GET /users. Filter via `params`. Returns { data:[...], pagination }.

Endpoints

URLTransportStateLatencyChecked
https://raisely.usefulapi.io/mcp streamable-http answering 206 ms 15 min ago

Alternatives to Raisely

same job, measured the same way
Mailchimp
by usefulapi

Read audiences, members, campaigns and reports; add, update, tag and archive subscribers.

18 tools answering
Pipedrive
by usefulapi

Read deals, persons, organizations, activities and pipelines; create and update CRM records.

19 tools answering
Orcid
by smaboundless

Search ORCID researcher profiles, retrieve works, and export citations

59 installs/wk local only
Git Leaderboard
by hrvoje0099

Official MCP server for Git Leaderboard rankings, profiles, streaks, and user comparisons.

27 installs/wk local only
I
PDF Generator
by mcp-z

MCP server for creative PDF generation with full emoji, Unicode, and offline support

370 installs/wk local only
Mana Public
by mana

Read-only MCP tools for Mana public creations, tags, creator profiles, and share pages.

6 tools answering
Decaframe
by decaframe

Presentations, slides, reports and one-pagers your agent designs and you edit. Exports to one file.

448 installs/wk local only
Presscart
by presscart

Browse 1,700+ publications and manage Presscart media placement campaigns, orders, and articles.

answering

Raisely — questions

Answers built from our own checks of this server.

What can Raisely do?
It exposes 23 tools, read directly from the server on our last check. Among them: create_donation, create_post, get_authenticated_user, get_campaign, get_donation, get_profile and 17 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Raisely mostly used for?
Its tools cluster around campaign, donation and profile. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Raisely working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 179 ms. The bar chart above shows every period we have measured.
How do I connect Raisely?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Raisely need an API key?
No. Raisely completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 23 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Raisely?
It answers our handshake in 179 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Raisely open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.