# MCP Integration (/docs/verdent-for-vscode/advanced-features/mcp)

> Extend Verdent with Model Context Protocol servers and plugins



### What You'll Learn [#what-youll-learn]

Overview of Model Context Protocol (MCP) integration in Verdent for VS Code, including setup, configuration, and extensibility options.

<Info>
  Comprehensive MCP documentation is currently being developed. This page provides an overview of MCP capabilities with detailed guides coming soon. Contact [support@verdent.ai](mailto:support@verdent.ai) for specific integration questions.
</Info>

***

## What is MCP (Model Context Protocol)? [#what-is-mcp-model-context-protocol]

Model Context Protocol (MCP) is an integration system that extends Verdent's capabilities by connecting to external tools, data sources, and services.

**Core Concept:**
MCP enables Verdent to interact with systems beyond its built-in tool set, allowing seamless integration with:

* External APIs and web services
* Database systems
* Cloud platforms (AWS, Azure, GCP)
* Project management tools
* CI/CD pipelines
* Custom internal tools

**Architecture:**
MCP servers act as bridges between Verdent and external systems. Each MCP server exposes specific capabilities that Verdent can invoke during coding sessions, similar to built-in tools like `file_read` or `bash`.

**Configuration Storage:**
MCP server configurations are stored in `~/.verdent/mcp.json` and managed through the Settings menu.

***

## Benefits of MCP Integration [#benefits-of-mcp-integration]

### Extended Capabilities [#extended-capabilities]

**Access External Systems:**
Connect Verdent to tools and services not available through built-in functionality. Query databases, interact with cloud services, or integrate project-specific APIs without leaving your coding workflow.

**Custom Tool Development:**
Create MCP servers tailored to your project's unique requirements. Build specialized integrations for internal tools, proprietary APIs, or domain-specific systems.

### Interoperability [#interoperability]

**Ecosystem Leverage:**
Tap into the growing MCP ecosystem. Community-developed MCP servers provide pre-built integrations for popular tools and services.

**Standardized Protocol:**
MCP provides a consistent interface for tool integration, ensuring new capabilities integrate smoothly with Verdent's existing tool system.

### Workflow Automation [#workflow-automation]

**Seamless Integration:**
MCP servers become part of Verdent's tool set. The agent automatically uses MCP tools when appropriate, or you can explicitly invoke them for specific tasks.

**Context-Aware Operations:**
MCP integrations understand your codebase context, enabling intelligent interactions with external systems based on current development state.

***

## Setting Up MCP Servers [#setting-up-mcp-servers]

### Configuration Process [#configuration-process]

**Access MCP Settings:**

1. Open Settings menu in Verdent
2. Navigate to **MCP Servers** section
3. View or modify `~/.verdent/mcp.json` configuration

**Configuration File:**
MCP servers are configured through the `~/.verdent/mcp.json` file, which defines server connections, authentication, and integration parameters.

<Note>
  Detailed MCP configuration schema and setup instructions are being finalized. For immediate assistance with MCP server setup, consult the MCP protocol specification or contact Verdent support.
</Note>

### Configuration Management [#configuration-management]

**Adding Servers:**
Configure new MCP servers by adding entries to `mcp.json` with connection details and authentication credentials.

**Multiple Servers:**
Verdent supports multiple concurrent MCP servers, allowing integration with several external systems simultaneously.

**Testing Connections:**
Validate MCP server configurations to ensure successful connections before using them in development workflows.

***

## MCP Plugins and Extensions [#mcp-plugins-and-extensions]

### Available Plugins [#available-plugins]

MCP plugins provide pre-built integrations for common tools and services.

<Info>
  A curated list of available MCP plugins is being compiled. Check the official Verdent documentation or MCP ecosystem resources for current plugin availability.
</Info>

**Expected Plugin Categories:**

* **Database Integrations:** PostgreSQL, MySQL, MongoDB query tools
* **Cloud Services:** AWS, Azure, GCP API interactions
* **Developer Tools:** GitHub, GitLab, Jira, Linear integrations
* **CI/CD Platforms:** Jenkins, GitHub Actions, CircleCI
* **Monitoring Services:** Datadog, New Relic, Sentry
* **Communication:** Slack, Discord, Microsoft Teams notifications

### Plugin Installation [#plugin-installation]

**Installation Methods:**
Plugins are installed and configured through the MCP Settings interface, typically requiring:

* Plugin identifier or source
* Configuration parameters
* Authentication credentials (if applicable)

**Dependency Management:**
MCP plugins may have dependencies on external services or libraries. Installation processes handle dependency resolution automatically when possible.

***

## Custom MCP Server Development [#custom-mcp-server-development]

### Creating Custom Servers [#creating-custom-servers]

Advanced users can create custom MCP servers to integrate proprietary tools or domain-specific systems.

**Development Approach:**
Custom MCP servers implement the MCP protocol specification, exposing tool capabilities that Verdent can invoke.

**Use Cases for Custom Servers:**

* **Internal API Integration:** Connect to company-specific APIs and services
* **Legacy System Bridges:** Enable Verdent to interact with legacy infrastructure
* **Specialized Data Sources:** Access proprietary databases or data warehouses
* **Workflow Automation:** Trigger custom build, deployment, or testing pipelines

<Note>
  Comprehensive custom MCP server development guides, including protocol implementation requirements, SDK documentation, and testing tools, are in development. For immediate custom integration needs, refer to the MCP protocol specification.
</Note>

### Integration Patterns [#integration-patterns]

**Workspace-Level Configuration:**
MCP servers can be configured at workspace level for project-specific integrations, enabling teams to share MCP configurations through version control.

**Tool Interoperability:**
MCP-provided tools integrate seamlessly with Verdent's built-in tools (`file_read`, `bash`, `spawn_subagent`), enabling complex workflows combining multiple tool types.

***

## MCP Workflow Examples [#mcp-workflow-examples]

### Database Query Integration [#database-query-integration]

**Scenario:** Query production database for debugging data issues.

**MCP Approach:**

```
User: "Check the orders table for customer ID 12345"
Verdent: [Uses MCP database server to execute safe read-only query]
        Results: 3 orders found for customer 12345
        [Displays formatted results]
```

The MCP database server handles authentication, query validation, and result formatting.

### Cloud Service Interaction [#cloud-service-interaction]

**Scenario:** Check AWS Lambda function logs for errors.

**MCP Approach:**

```
User: "Show me recent errors from the payment-processor Lambda function"
Verdent: [Invokes MCP AWS integration]
        [Retrieves CloudWatch logs for specified function]
        [Filters for ERROR level entries]
        [Presents formatted error summaries]
```

MCP AWS server manages authentication, API calls, and log parsing.

### CI/CD Pipeline Monitoring [#cicd-pipeline-monitoring]

**Scenario:** Check build status before deploying changes.

**MCP Approach:**

```
User: "Is the main branch build passing?"
Verdent: [Queries MCP CI/CD integration]
        Build #245: ✓ Passed (2 minutes ago)
        All tests passed, ready for deployment
```

MCP CI/CD server tracks pipeline status and provides real-time feedback.

***

## Security Considerations [#security-considerations]

### Authentication & Authorization [#authentication--authorization]

**Credential Management:**
MCP servers handle authentication to external services. Credentials are stored securely in MCP configuration and never exposed in chat history or code.

**Permission Scoping:**
Configure MCP servers with minimal necessary permissions. Use read-only access where possible, and restrict destructive operations.

### Safe Operations [#safe-operations]

**Command Review:**
Operations involving MCP tools can be reviewed in Manual Accept Mode before execution, providing visibility and control.

**Audit Logging:**
MCP server operations appear in Verdent's chat history, creating an audit trail of external system interactions.

***

## Troubleshooting MCP Integration [#troubleshooting-mcp-integration]

### Common Issues [#common-issues]

**Connection Failures:**

* Verify network connectivity to MCP server
* Check authentication credentials in `mcp.json`
* Ensure MCP server is running and accessible
* Validate configuration file syntax

**Permission Errors:**

* Confirm API keys or credentials have required permissions
* Check service quotas or rate limits
* Verify firewall rules allow MCP traffic

**Tool Invocation Issues:**

* Ensure MCP server exposes expected tools correctly
* Check tool parameter formats match server expectations
* Review MCP server logs for error details

### Getting Help [#getting-help]

**Support Channels:**

* Verdent support: [support@verdent.ai](mailto:support@verdent.ai)
* [MCP protocol documentation](https://modelcontextprotocol.io)
* [Verdent Discord community](https://discord.com/invite/NGjXEZcbJq) for real-time support

**Diagnostic Information:**
When reporting MCP issues, provide:

* MCP server type and version
* Configuration details (sanitized of credentials)
* Error messages from chat history
* MCP server logs (if accessible)

***

## MCP Documentation Resources [#mcp-documentation-resources]

### Official Documentation [#official-documentation]

<Info>
  Comprehensive MCP integration guides are being developed, including:

  * Complete MCP protocol specification
  * Server development SDK documentation
  * Plugin marketplace and registry
  * Integration examples and tutorials
  * API reference for custom server development
</Info>

**Coming Soon:**

* Step-by-step MCP server setup guides
* Plugin installation and configuration walkthroughs
* Custom server development tutorials
* Best practices for MCP integration
* Performance optimization for MCP workflows

### Interim Resources [#interim-resources]

**Current MCP Information:**

* MCP protocol specification (external)
* Community-developed MCP servers and examples
* MCP ecosystem GitHub repositories

**Contact for Details:**
For immediate MCP integration assistance, contact [support@verdent.ai](mailto:support@verdent.ai) with your specific use case and integration requirements.

***

## See Also [#see-also]

<CardGroup cols="2">
  <Card title="Tool Reference" icon="wrench" href="/docs/verdent-for-vscode/advanced-features/tool-reference">
    Built-in tool capabilities
  </Card>

  <Card title="Extensibility" icon="puzzle-piece" href="/docs/verdent-for-vscode/advanced-features/extensibility">
    Other extension methods
  </Card>

  <Card title="Configuration" icon="gear" href="/docs/verdent-for-vscode/configuration/settings">
    Verdent settings and preferences
  </Card>

  <Card title="Best Practices" icon="lightbulb" href="/docs/verdent-for-vscode/best-practices/prompts">
    Effective prompting techniques
  </Card>
</CardGroup>