Using Pylee
How to Configure MCP Servers on PyleeAI
This tutorial will walk you through the proper way to configure and connect a new MCP server using PyleeAI’s MCP hosting and private registry management platform.
This tutorial assumes you have access to an MCP server that you would like to use directly within hosts or within a public or private collection or “registry” of servers to share with your team.
Once you’re done, confirm by clicking “Create server namespace”.
Solution: You can proceed with the next steps regardless.
Prerequisites
Before you begin, ensure you have:- ✅ An MCP server that is already running
- ✅ Required API keys or other secrets/environment variables for the server
- ✅ An MCP host that you’ve tested
Step 1: Start Server Configuration
- On the main PyleeAI dashboard, navigate to the Configure New Server section
- Click “Configure Your Server”
Step 2: Confirm You Have a Server Running
You will now land on an interstitial page that will remind you that you must have access to a server that is running in order to proceed. This page provides an overview of what to expect. Pylee supports both remote or local connections. Once you’re confident, confirm by clicking the “I’ve Setup my Server” button.Step 3: Create the Namespace of Your MCP Server
All servers must have a namespace to continue. A namespace is so that Pylee can guarantee your server won’t conflict with other servers in your organization.Fill in your server namespace details:
| Field | Description |
|---|---|
| Organization | The organization you’d like to associate your MCP server with. If you haven’t made an organization for your team, this will default to your personal organization made at onboarding. |
| Server namespace | The name of your MCP server. This must be unique within your organization. You cannot change this later. |
| Description | An optional description of your server, rendered in markdown. You can edit the markdown at any time. |
| Public/Private Toggle | This is important. This decides whether your server (along with secrets/env variables configured on the server level) is available to all users on Pylee, or just within your organization (private). You can edit this later. |
Step 4: Configure Your Server
So far you’ve only made the unique domain for your server, now it’s time to actually configure it. You will see a series of steps to complete. These can be completed in any order and not all steps are required for every server, however a recommended order is proposed. The main requirements are to create a server version and specify where your MCP server is running (remote or local).Step 5: Create a Server Version
Click “Create Version” to set up a new server version.Fill in your version details:
- Organization: Which organization your new server version will be associated with
- Version: An alphanumeric string to use as your designation
- Base this version on: Decided whether to base on a new or existing version. First time servers with no versions will not see this option and will assume an empty version. Note that empty version will not inherit any remotes or packages set in previous versions.
Step 6: Choose Connection Method: Remotes and/or Packages
You will now decide to point PyleeAI to your actual MCP server and configure any secret, environment variable, or header templates needed to run.⚠️ Important Security WarningChoose Remote or Package
Do not put actual keys here unless you’re comfortable with the internet having access to it. You will configure anything private at the Organization or Registry level.
Step 7a: Configure Remotes Templates
If your MCP server has a remote endpoint via Streamable or Server Side Events (SSE), click “Configure Remotes”.Specify your remote configuration:
URL
- URL: endpoint of your MCP server
Headers
Clicking “Add Headers” will expand to:- Name: String key of the header
- Value: String value placeholder to be populated later, place in curly brackets
- Description: Optional description
- Required Toggle: Whether the header is required for a user to interact
- Secret Toggle: Whether the header contains sensitive information. This is part of the MCP spec.
⚠️ Security Note
Do NOT put sensitive information directly here, whether or not the Secret toggle is enabled.
Step 7b: Configure Packages Templates
If your MCP server is hosted in a package registry such as npm, PyPI, docker, or homebrew, then configure your package details:Package Settings
- Registry: Choose npm, Docker, PyPI, or Homebrew
(These are NOT your PyleeAI MCP registry) - Name: Your package name on the specified package registry
- Version: Which version to call (default to latest)
- Runtime Hint: Any startup arguments
- Package Arguments: Additional arguments
Environment Variables
These are placeholder key values to specify in org or registry settings:- Name: The key of the environment variable configured on the MCP server
- Value: The key that will be displayed in your PyleeAI organization or registry secrets page. NOT the actual value. Must be in curly brackets
- Required Toggle: Whether the header is required for a user to interact
- Secret Toggle: Whether the header contains sensitive information. This is part of the MCP spec.
⚠️ Security Reminder
Do NOT put sensitive information directly here, whether or not the Secret toggle is enabled.
Step 8: Add Secrets to Organization
Now you’ll store your actual API keys securely in your organization settings.Navigate to Organization Settings
- Look for the PyleeAI omega logo and click your organization name (e.g.,
nickdegiacomo) - Click on your username/organization name in the breadcrumb navigation at the top left of your window
- This is your organization page. Go to Settings → Secrets
- Click “New organization secret”
Add Your Secret
Configure your secret with these details:- Name: Must match what’s in your curly brackets from Step 7a or 7b (remove the curly brackets)
- Value: Your actual API key
Step 9: Connect to Your Client
Once your package is configured with template placeholders:For VS Code/Cursor
- Click the green “Connect” button
- Choose “Open in VS Code” or “Open in Cursor”
- This will automatically deep-link to your client with the proper configuration
For Other Clients
- Click “Other connections”
- Select your client from the list
- Copy the provided configuration
- Paste it into your client’s MCP configuration file
Understanding the UI Elements
Local/Remote Tabs
If you see “Local” and “Remote” options under the Connect button, these are tabs, not clickable buttons. They only appear when you have multiple connection methods available.Raw JSON Configuration
The expandable JSON config section shows a generic configuration that can be adapted for different clients. The “Open in VS Code/Cursor” buttons provide client-specific configurations automatically.Troubleshooting
Onboarding Checkmarks Not Updating
Issue: Checkmarks may not update even when steps are completed correctly and block me from proceeding.Solution: You can proceed with the next steps regardless.
Connection Not Working
Check these common issues:- Ensure your local server is running before testing
- Check that your package name and arguments are correct
- Verify your template placeholder matches your organization secret name exactly