MCP Anthropic Server (

Created By
mystique920a year ago
MCP-Server to query the experimental Anthropic Prompt Tools API
Overview

What is MCP Anthropic Server?

MCP Anthropic Server is a Model Context Protocol (MCP) server designed to interact with Anthropic's experimental prompt engineering APIs, allowing users to generate, improve, and templatize prompts for various tasks.

How to use MCP Anthropic Server?

To use the MCP Anthropic Server, clone the repository, install the necessary dependencies, configure your Anthropic API key, and start the server to listen for MCP connections.

Key features of MCP Anthropic Server?

  • Generate Prompt: Create prompts based on task descriptions.
  • Improve Prompt: Enhance existing prompts using feedback.
  • Templatize Prompt: Convert specific prompts into reusable templates.

Use cases of MCP Anthropic Server?

  1. Generating prompts for AI models based on specific tasks.
  2. Improving prompt quality through iterative feedback.
  3. Creating templates for common prompt structures to streamline prompt engineering.

FAQ from MCP Anthropic Server?

  • What is the purpose of the MCP Anthropic Server?

It provides tools to facilitate prompt engineering for AI models, enhancing the interaction quality with the models.

  • Is there a cost associated with using the server?

The server itself is free to use, but you will need an API key from Anthropic, which may have associated costs depending on usage.

  • Can I run this server locally?

Yes, you can run the server locally after setting it up according to the provided instructions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mystique920
Star
1
Language
TypeScript
License
ISC license
Tags

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