Back to Home
cursor icon

mcp-servers

Verified Safe

by cursor

Overview

Provides a curated collection of Model Context Protocol (MCP) server configurations to enable AI agents to interact with various developer tools and services.

Installation

Run Command
No command provided

Environment Variables

  • VAULT_ADDR
  • VAULT_TOKEN
  • VAULT_NAMESPACE
  • PAGERDUTY_USER_API_KEY
  • PAGERDUTY_API_HOST
  • TFE_ADDRESS
  • TFE_TOKEN
  • ENABLE_TF_OPERATIONS
  • FIRECRAWL_API_KEY
  • GITHUB_PERSONAL_ACCESS_TOKEN
  • BROWSERBASE_API_KEY
  • BROWSERBASE_PROJECT_ID
  • SONARQUBE_TOKEN
  • SONARQUBE_URL
  • STRIPE_SECRET_KEY
  • HEROKU_API_KEY
  • FASTMCP_LOG_LEVEL
  • AWS_DOCUMENTATION_PARTITION
  • SELECT_STAR_TOKEN
  • POSTHOG_AUTH_HEADER
  • DBT_MCP_HOST
  • MULTICELL_ACCOUNT_PREFIX
  • DBT_TOKEN
  • DBT_PROD_ENV_ID
  • DBT_DEV_ENV_ID
  • DBT_USER_ID
  • DBT_PROJECT_DIR
  • DBT_PATH
  • DISABLE_DBT_CLI
  • DISABLE_SEMANTIC_LAYER
  • DISABLE_DISCOVERY
  • DISABLE_REMOTE
  • DEBUG
  • motherduck_token

Security Notes

The repository itself is a collection of JSON configurations and a README generation script, which are safe. The primary security considerations arise from executing the defined MCP servers, many of which use 'npx' to run external npm packages or 'docker run' to execute Docker images. While the '-y' flag with 'npx' bypasses prompts, the repository is a curated list, implying some level of vetting. Users must ensure the trustworthiness of the third-party MCP server packages/images they choose to run. Many servers require sensitive API keys or tokens, which are expected to be provided via environment variables, mitigating hardcoded secret risks in the repository itself, but shifting that responsibility to the user's environment setup.

Similar Servers

Stats

Interest Score75
Security Score7
Cost ClassLow
Avg Tokens10
Stars118
Forks46
Last Update2025-11-24

Tags

MCPAPIDeveloper ToolsAI AgentsIntegrations