Highrise MCP Server by CData

Created By
CDataSoftwarea year ago
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Highrise (beta): https://www.cdata.com/download/download.aspx?sku=BHZK-VZK-V&type=beta
Overview

What is Highrise MCP Server by CData?

Highrise MCP Server by CData is a read-only Model Context Protocol (MCP) server designed to allow large language models (LLMs) to query live data from Highrise using natural language, without the need for SQL.

How to use Highrise MCP Server?

To use the Highrise MCP Server, clone the repository, build the server, install the CData JDBC Driver for Highrise, configure your connection, and create a configuration file for your AI client (e.g., Claude Desktop).

Key features of Highrise MCP Server?

  • Provides a read-only interface to Highrise data.
  • Allows querying of live data using natural language.
  • Supports integration with various AI clients.

Use cases of Highrise MCP Server?

  1. Querying customer data from Highrise using natural language.
  2. Integrating with AI tools for data analysis and reporting.
  3. Simplifying data access for non-technical users.

FAQ from Highrise MCP Server?

  • Can I write data to Highrise using this server?

No, this server is read-only. For write capabilities, consider the full CData MCP Server for Highrise.

  • Is there a cost to use the Highrise MCP Server?

The server is free to use, but requires a license for the CData JDBC Driver.

Server Config

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\highrise.prp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago