Chapel Support for MCP

Created By
DanilaFea year ago
A Model-Context-Protocol (MCP) server for AI Agents to make use of Chapel
Overview

What is Chapel Support for MCP?

Chapel Support for MCP is a server designed to facilitate the use of the Chapel programming language within AI agents, providing tools for code compilation, linting, and access to educational resources.

How to use Chapel Support for MCP?

To use the Chapel Support server, clone the repository, set up a virtual environment, and run the server using the provided command. Integrate it with AI assistants by configuring them to connect to this server.

Key features of Chapel Support for MCP?

  • Access to Chapel educational primers
  • Direct compilation of Chapel code through the API
  • Linting capabilities to ensure code quality
  • Automatic detection of Chapel installation directory

Use cases of Chapel Support for MCP?

  1. Assisting developers in learning and using Chapel effectively.
  2. Providing a platform for AI tools to interact with Chapel code.
  3. Enabling automated code quality checks for Chapel projects.

FAQ from Chapel Support for MCP?

  • What is Chapel?

Chapel is an open-source parallel programming language designed for productive parallel computing.

  • What are the prerequisites for using this project?

You need Python 3.13 or higher and the Chapel programming language installed.

  • Can I contribute to this project?

Yes! Contributions are welcome through pull requests or issue submissions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DanilaFe
Star
0
Language
Python
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