Skip to content
Prompt

mcp-curl — Copilot Instructions

by sixees

AI Summary

A prompt-based MCP server that enables Claude and ChatGPT to execute cURL commands directly, ideal for developers who need to integrate HTTP requests into their AI workflows.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "mcp-curl — Copilot Instructions" prompt rules to my project.
Repository: https://github.com/sixees/mcp-curl

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

Simple MCP server to execute cURL commands - ideal for Desktop AI Clients (Claude / ChatGPT, etc)

Copilot Instructions

This repository is a JavaScript/TypeScript library/application. When generating or suggesting code, reinforce and follow the principles and objectives outlined below:

1. Efficiency and Performance

• Prefer fast, efficient code with minimal runtime overhead. • Avoid unnecessary iterations, blocking operations, and patterns that cause memory leaks. • Use appropriate data structures (Map/Set over Object/Array when beneficial for lookups). • Prefer async/await patterns; avoid callback hell and unnecessary synchronous operations. • Be mindful of bundle size—prefer tree-shakeable imports and lightweight dependencies. • Use memoization or caching for expensive computations when appropriate. • Avoid unnecessary re-renders in UI frameworks (React, Vue, etc.).

2. JavaScript/TypeScript Best Practices

• Use modern ES6+ syntax (const/let over var, arrow functions, destructuring, template literals). • Provide TypeScript types or JSDoc annotations for all public APIs and complex functions. • Prefer named exports over default exports for better tree-shaking and refactoring. • Use dependency injection or module patterns; avoid hard-coded dependencies. • Validate inputs at module boundaries using schema validation (Zod, Yup, Joi) for complex cases. • Follow consistent module organization (barrel files, feature-based folders). • Prefer pure functions and immutable data patterns where practical. • Use Promises or async/await consistently—never mix callbacks and promises. • Handle all Promise rejections and async errors appropriately.

3. SRP & DRY Principles

• Avoid code duplication (DRY). Extract repeated logic into reusable functions or modules. • Follow the Single Responsibility Principle (SRP): • Entry points/handlers should be thin, delegating business logic to services or utilities. • Modules/classes should handle one logical concern (not mixing unrelated tasks). • Prefer composition over inheritance for code reuse. • Extract complex conditionals into well-named functions or constants.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
AdoptionUnder 100 stars
1 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars1
Issues0
Updated1mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more