Onx Mcp Server

Created By
StevanFreeborna year ago
A Model Context Protocol (MCP) server implementation that integrates with Onspring's API, allowing AI assistants to access and manipulate data stored in Onspring instances.
Overview

What is onx-mcp-server?

The onx-mcp-server is a project aimed at exploring the model context protocol by building a simple MCP server that facilitates access to data stored in Onspring instances through the Onspring API.

How to use onx-mcp-server?

To use the onx-mcp-server, clone the repository from GitHub, set up your environment with the necessary dependencies, and run the server to start accessing data via the Onspring API.

Key features of onx-mcp-server?

  • Simple implementation of an MCP server
  • Access to Onspring data through a standardized API
  • Built using TypeScript for better maintainability

Use cases of onx-mcp-server?

  1. Integrating Onspring data into other applications.
  2. Building custom data retrieval solutions for Onspring users.
  3. Experimenting with the model context protocol in a server environment.

FAQ from onx-mcp-server?

  • What is the model context protocol?

The model context protocol is a framework for accessing and manipulating data in a structured way.

  • Is onx-mcp-server open source?

Yes! The onx-mcp-server is open source and available under the MIT license.

  • What programming language is used?

The project is built using TypeScript.

Server Config

{
  "mcpServers": {
    "onx-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@stevanfreeborn/onx-mcp-server"
      ],
      "env": {
        "ONSPRING_API_KEY": "your_onspring_api_key",
        "ONSPRING_BASE_URL": "https://api.onspring.com"
      }
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
StevanFreeborn
Star
0
Language
TypeScript
License
MIT license
Category

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)

a day ago