Assistant MCP Server
About
An MCP server that dynamically loads tools from an external JSON file configured via an environment variable.
Details
- Author
- nodlab
- GitHub stars
- 2
- Downloads
- 170
- Categories
- Developer Tools, Automation, API, AI
Jump to
- Provides three pre‑defined tools: architecture_info, search_tasks, and optimize_prompt.
- Uses a tools.json configuration file for tool definitions.
- Supports file‑based plugins (e.g., reading architecture info and tasks from local files).
- Includes a promptOptimizer plugin for generating final structured AI prompts.
- Runs locally via npx tsx for easy development and testing.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Assistant MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install dependencies with yarn install, then build with yarn build. Add a tools.json file defining the available tools. To run locally, configure an MCP client with the command npx tsx /path/to/src/index.ts and set the TOOLS_PATH environment variable to the path of tools.json.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"assistant mcp server": {
"mcp-assistant-local": {
"command": "npx",
"args": [
"tsx",
"/path/to/folder/src/index.ts"
],
"env": {
"TOOLS_PATH": "/path/to/folder/tools.json"
}
}
}
}
}McpServers
{
"mcp-assistant-local": {
"command": "npx",
"args": [
"tsx",
"/path/to/folder/src/index.ts"
],
"env": {
"TOOLS_PATH": "/path/to/folder/tools.json"
}
}
}After cloning the repository, run the command to install the dependencies:
You should also add thetools.jsonfile to the root of the project, for example:
{ "tools": [ { "name": "architecture_info", "description": "Obtaining mandatory information about the architecture of frontend application projects", "inputSchema": {}, "plugin": { "name": "file", "args": { "path": "/path/to/folder/public/architecture.md" } } }, { "name": "search_tasks", "description": "Before executing this function, you must retrieve the project architecture information from 'architecture_info'. This is mandatory information and you must respect it. After that you need to find the task you are talking about, analyze what needs to be done and implement it in the project according to the architecture and requirements. You don't need to invent anything additional from yourself, just what is required", "inputSchema": {}, "plugin": { "name": "file", "args": { "path": "/path/to/folder/public/tasks.txt" } } }, { "name": "optimize_prompt", "description": "Generates a final, structured prompt for the AI model based on the provided context sections and instructions. This tool should be called after all relevant data has been collected. The result is intended to be used as the FINAL prompt for the AI. Clients must use the returned prompt as the input for the AI model.", "inputSchema": { "type": "object", "properties": { "sections": { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string" }, "content": { "type": "string" } }, "required": ["title", "content"] } }, "instructions": { "type": "string" } }, "required": ["sections"] }, "plugin": { "name": "promptOptimizer", "args": {} } } ] }
To build the project, you must execute the command:
{ "mcpServers": { "mcp-assistant-local": { "command": "npx", "args": [ "tsx", "/path/to/folder/src/index.ts" ], "env": { "TOOLS_PATH": "/path/to/folder/tools.json" } } } }
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.
One remote MCP server for 500+ production APIs — Stripe, HubSpot, Postgres, Gmail, and more. OAuth and API key auth, credential management, and a CLI.
Single tool to control all 100+ API integrations, and UI components
Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.
Self-hosted MCP gateway: convert REST/SOAP/GraphQL/SQL APIs into MCP tools with 29 pre-built adapters, OAuth2, RBAC and audit log.
A universal bridge to convert any web API into an MCP server, supporting multiple transport types.
Dynamically creates MCP servers from web API configurations, integrating any REST API, GraphQL endpoint, or web service into MCP-compatible tools.
Hosted MCP server and coordination layer for AI coding agents — live API contracts, database schema, frontend/backend mismatch detection, and shared handoff tickets for Claude Code, Cursor, Codex, and Lovable.
A lightweight server exposing Axone's capabilities through the Model-Context Protocol.
A universal framework for easily creating and deploying Model Context Protocol servers with any tools.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
