Custom Context MCP Server

Created By
omer-ayhana year ago
This Model Context Protocol (MCP) server provides tools for structuring and extracting data from text according to JSON templates.
Overview

What is Custom Context MCP Server?

The Custom Context MCP Server is a Model Context Protocol (MCP) server designed to provide tools for structuring and extracting data from text according to JSON templates.

How to use Custom Context MCP Server?

To use the server, install the necessary dependencies with npm install, then run the server using npm start. For development with hot reloading, use npm run dev:watch.

Key features of Custom Context MCP Server?

  • Text-to-JSON transformation for structured data extraction
  • Grouping and structuring text based on JSON templates
  • Support for arbitrary JSON structures with nested placeholders
  • Intelligent extraction of key-value pairs from text
  • Custom hot reloading setup for development

Use cases of Custom Context MCP Server?

  1. Structuring AI-generated text into JSON format for data analysis.
  2. Automating data extraction from unstructured text sources.
  3. Facilitating integration of AI outputs into downstream applications.

FAQ from Custom Context MCP Server?

  • What is the purpose of the MCP server?

The MCP server helps in structuring and extracting data from text using predefined JSON templates.

  • Is there a specific format for JSON templates?

Yes, templates can include placeholders defined with angle brackets and must be valid JSON strings.

  • Can I use this server for any type of text?

Yes, the server is designed to work with any text that can be structured according to the provided JSON templates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
omer-ayhan
Star
0
Language
TypeScript
License
MIT 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)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago