🤖 Phrases MCP Server

An advanced, streamlined MCP (Model Context Protocol) repository engineered for the meticulous management of inspirational quotations. This backend service is designed for frictionless interfacing with Claude for Desktop and any compliant MCP client.

✨ Core Functionality

• Comprehensive Content Lifecycle Management - Facilitates the creation, querying, modification, and purging of textual entries with ease.
• Seamless Claude for Desktop Synergy - Enables direct operational access to your curated phrase corpus from within the Claude application.
• Built-in Mock API Layer - Includes a simulated backend interface to support robust testing and initial development cycles.

🛠️ Exposed MCP Services

This server furnishes the following distinct MCP operational endpoints:

Service Name	Purpose
get-all-phrases	Retrieves the complete inventory of stored phrases.
get-phrase-by-id	Locates and returns a specific entry via its unique identifier.
get-phrase-by-name	Fetches entries associated with a specified author's appellation.
create-phrase	Establishes a new textual entry within the collection.
update-phrase	Modifies the textual content of an existing record.
delete-phrase	Eradicates a designated entry based on its ID.

🚀 Deployment Procedure

bash

Clone the source repository

git clone https://github.com/ronniemh/phrases-MCP-server.git cd phrases-MCP-server

Install requisite dependencies

npm install

Execute the build process

npm run build

🔌 Configuration for Claude for Desktop Integration

1. Obtain and install Claude for Desktop (ensure the most recent iteration is running).

2. Update the MCP server configuration within Claude for Desktop:

Navigate to the configuration file location (MAC/Linux):

~/Library/Application Support/Claude/claude_desktop_config.json

1. Inject the server configuration block:

{ "mcpServers": { "phrases": { "command": "node", "args": [ "/ABSOLUTE/PATH/TO/phrases/build/index.js" ] } } }

1. Restart the Claude for Desktop application to load the new configuration.

💡 Interactive Usage Examples within Claude

Once integrated, direct interaction with the phrase repository is possible:

• "Display every available textual entry."
• "Query phrases attributed to [Author Name]."
• "Instantiate a new entry for [Source] containing the text: [Content]."
• "Revise the record identified by ID [Numeric ID] to state [New Text]."
• "Obliterate the entry corresponding to ID [Numeric ID]."

🧪 Validation & Testing

⚠️ Crucial Prerequisite: Adjusting TypeScript Configuration

Prior to executing any tests, you must temporarily revise the compilerOptions within tsconfig.json as follows:

"compilerOptions": { "target": "ES2020", "module": "NodeNext", "moduleResolution": "NodeNext", "esModuleInterop": true, "outDir": "build", "strict": true }

Memo: Remember to revert these settings to their original state after testing to ensure the primary MCP server compilation functions correctly.

To initiate the validation suite:

bash npm run test:requests

This command triggers a sequence of assertions that perform creation, fetching, modification, and destruction operations against the simulated API backend.

🏗️ Project Blueprint

src/ ├── helpers/ │ └── makeMockAPIRequest.ts # Utility functions for API interaction ├── index.ts # Primary entry point and service interface definition └── testRequest.ts # Script dedicated to API function verification

🔄 Development Lifecycle

1. Implement modifications within the src/ directory.
2. Recompile using npm run build.
3. Verify functionality via npm run test:requests.
4. Apply changes by restarting Claude for Desktop.

🔍 MockAPI Backend Configuration Details

This deployment leverages MockAPI as the provisional persistence layer for content storage and routing. The currently hardcoded base endpoint is:

https://67ec86aeaa794fb3222e0682.mockapi.io/frases/api/v1/user

Establishing a Personalized MockAPI Endpoint

1. Register for an account at MockAPI.
2. Provision a new project instance.
3. Create a resource labeled user defining these attributes:
4. id (Type: number, Automatic Generation enabled)
5. name (Type: string)
6. phrase (Type: string)
7. Capture the resulting API endpoint URL.
8. Update the constant BASE_URL within the src/helpers/makeMockAPIRequest.ts file:

typescript // Substitute this placeholder with your custom MockAPI endpoint const BASE_URL = "https://your-project.mockapi.io/your-path/user";

📝 Supplementary Information

• This configuration relies on a mock API for data retention; consider migrating to a robust, dedicated database solution for production deployments.
• The project structure adheres strictly to the established MCP documentation standards to maximize long-term maintenance feasibility.
• If communication issues arise with the mock service, review potential constraints imposed by MockAPI's free-tier usage policy.

📄 Governance

ISC