Rise Mcp

io.github.gzloPublished by GitHub account gzlov1.0.3Updated Oct 24, 2026

RISE CRM MCP server — 36 tools across CRM, projects, tickets, finance, sales, HR, and reports.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

A local MCP server that connects an assistant to a RISE CRM instance, exposing 36 tools across CRM, projects, tickets, finance, sales, HR and reports.

What you can do
Work with CRM records such as contacts, leads and customers through the CRM tools. Manage projects and support tickets. Handle finance, sales and HR data. Produce reports from the connected RISE CRM instance.
When to use it
Useful when your team runs RISE CRM and you want an assistant to read or act on CRM, project, ticket, finance, sales or HR data without switching apps. Best suited to users who already have a RISE CRM instance and API access.
Requirements
Runs locally as an npm package (rise-mcp) over stdio, so Node.js is needed. Requires a RISE CRM instance and two environment variables: RISE_API_URL with the instance base URL and RISE_API_KEY with an API key generated in RISE CRM settings. Desktop only.
Before you install
The API key in RISE_API_KEY grants access to your CRM data and should be treated as a secret. The tools span CRM, finance, sales and HR records, so expect reads and possibly writes to business data; check what each tool changes before use. Data goes to your own RISE CRM instance.

Installation

In SourceWeft

  1. Open Rise Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.