MCP Made Easy

What's an MCP Server?

MCP servers are specialized extensions that enhance PostQode's capabilities. They enable PostQode to perform additional tasks like fetching web pages, processing images, accessing APIs, and much more.

MCP Marketplace Walkthrough

The MCP Marketplace provides a one-click installation experience for hundreds of MCP servers across various categories.

1. Access the Marketplace

• In PostQode, click the "Extensions" button (square icon) in the top toolbar
• The MCP marketplace will open, showing available servers by category

2. Browse and Select a Server

• Browse servers by category (Search, File-systems, Browser-automation, Research-data, etc.)
• Click on a server to see details about its capabilities and requirements

3. Install and Configure

• Click the install button for your chosen server
• If the server requires an API key (most do), PostQode will guide you through:
  • Where to get the API key
  • How to enter it securely
• The server will be added to your MCP settings automatically

4. Verify Installation

• PostQode will show confirmation when installation is complete
• Check the server status in PostQode's MCP settings UI

5. Using Your New Server

• After successful installation, PostQode will automatically integrate the server's capabilities
• You'll see new tools and resources available in PostQode's system prompt
• Simply ask PostQode to use the capabilities of your new server
• Example: "Search the web for recent React updates using Perplexity"

Corporate Users: If you're using PostQode in a corporate environment, ensure you have permission to install third-party MCP servers according to your organization's security policies.

What Happens Behind the Scenes

When you install an MCP server, several things happen automatically:

1. Installation Process

• The server code is cloned/installed to /Users/<username>/Documents/PostQode/MCP/
• Dependencies are installed
• The server is built (TypeScript/JavaScript compilation or Python package installation)

2. Configuration

• The MCP settings file is updated with your server configuration
• This file is located at: /Users/<username>/AppData/Roaming/Code/User/globalStorage/postqode.postqode/settings/postqode_mcp_settings.json
• Environment variables (like API keys) are securely stored
• The server path is registered

3. Server Launch

• PostQode detects the configuration change
• PostQode launches your server as a separate process
• Communication is established via stdio or HTTP

4. Integration with PostQode

• Your server's capabilities are added to PostQode's system prompt
• Tools become available via use_mcp_tool commands
• Resources become available via access_mcp_resource commands
• PostQode can now use these capabilities when prompted by the user

Troubleshooting

Common Installation Issues

• Ensure your internet connection is stable
• Check that you have the necessary permissions to install new software
• Verify that the API key was entered correctly (if required)
• Check the server status in the MCP settings UI for any error messages

How to Remove an MCP Server

To completely remove a faulty MCP server:

1. Open the MCP settings file: /Users/<username>/AppData/Roaming/Code/User/globalStorage/postqode.postqode/settings/postqode_mcp_settings.json
2. Delete the entire entry for your server from the mcpServers object
3. Save the file
4. Restart PostQode

tip

Users can click on Delete server option from the MCP menu.

I'm Still Getting an Error

If you're getting an error when using an MCP server, you can try the following:

• Check the MCP settings file for errors
• Use a Claude Sonnet model for installation
• Verify that paths to your server's files are correct
• Ensure all required environment variables are set
• Check if another process is using the same port (for HTTP-based servers)
• Try removing and reinstalling the server (remove from both the postqode_mcp_settings.json file and the /Users/<username>/Documents/PostQode/MCP/ directory)
• Use a terminal and run the command with its arguments directly. This will allow you to see the same errors that PostQode is seeing