Claude Desktop can connect to remote MCP servers directly through Claude's connector system. For Deplion, that means Claude can work with publication tools from the same conversation where you create or edit a landing page.
The setup does not require a local MCP process. Deplion is added as a remote connector, then authorized through your Deplion account.
This guide covers the complete setup and the checks to run before using it on a real project.
Before you start
You need:
- a Claude account with access to custom connectors;
- Claude Desktop signed in to that account;
- a Deplion account;
- the Deplion MCP endpoint:
https://deplion.cc/mcp/deplion
Anthropic currently supports custom remote MCP connectors in Claude Desktop for Free, Pro, Max, Team, and Enterprise users. On Team and Enterprise plans, an organization owner may need to add the connector before members can connect to it.
Remote connector vs local MCP configuration
Claude Desktop supports more than one MCP connection model.
A local MCP server runs on your computer and may be configured through a desktop extension or local configuration.
Deplion uses a remote MCP connector instead. The connection is associated with your Claude account and authorized against Deplion.
That distinction matters because you should not add Deplion to claude_desktop_config.json as though it were a local stdio server.
Use Claude's connector interface instead.
Step 1: Open Connectors in Claude Desktop
In Claude Desktop:
- Open Customize.
- Select Connectors.
- Choose Add custom connector.
Depending on your Claude plan and organization settings, the exact controls may differ slightly.
For an individual account, the normal path is:
Customize → Connectors → + → Add custom connector
For Team and Enterprise organizations, an owner can add the connector at the organization level first. Members then connect and authorize it individually.
Step 2: Add the Deplion MCP URL
Enter this URL as the remote MCP server address:
https://deplion.cc/mcp/deplion
Finish adding the connector.
Claude should then start the authorization flow.
Do not add arbitrary headers or copy access tokens into the connector configuration. Use the authorization flow presented by Deplion.
Step 3: Authorize Claude in Deplion
Complete the Deplion sign-in and authorization steps shown in the browser.
The purpose of this step is to grant the connector access under your own Deplion account.
After authorization, return to Claude Desktop and confirm that the connector appears as connected.
If you use more than one Deplion account, check which account is active before approving access. Projects and actions available to Claude follow the authorized account context.
Step 4: Enable Deplion in the conversation
Adding a connector does not necessarily mean it is active in every conversation.
Open the conversation where you want Claude to work with Deplion, then enable the connector from the conversation's connector controls.
In current Claude interfaces, connectors can be enabled from the + menu near the message composer.
Once enabled, Claude can discover the tools exposed by the Deplion MCP server.
Step 5: Test the connection with a read-only request
Start with a low-risk request before asking Claude to change or publish anything.
For example:
Use the Deplion connector and show me my available projects. Do not change anything.
A successful response confirms three things:
- Claude can see the connector.
- Authorization succeeded.
- The MCP tools are available in the current conversation.
If Claude answers without using the connector, explicitly tell it to use Deplion.
Step 6: Create a small test project
After the read-only check, try a controlled write action.
Example:
Create a new Deplion project called MCP Connection Test.
Add a minimal index.html with a heading that says "MCP connection works".
Show me what you created before publishing it.
Review the result before the publication step.
Then ask:
Publish the current version of the MCP Connection Test project through Deplion.
This verifies the full path from Claude Desktop to Deplion.
A practical workflow for a real landing page
Once the connector works, you can keep the full publication workflow inside the conversation.
A typical request might be:
Create a responsive static landing page for a B2B analytics product.
Use semantic HTML, CSS, and client-side JavaScript.
Include a hero, benefits, social proof, FAQ, and a contact form.
Create a Deplion project for it.
Before publishing, review the files for broken links, placeholder text, and accidental secrets.
Then publish the reviewed version.
You can continue editing the same project with focused instructions:
Change only the hero headline and CTA copy.
Keep the current layout, colors, scripts, and form unchanged.
Preview the result before publishing a new version.
The advantage of this workflow is not that Claude becomes a different editor. It is that creation and publication can be coordinated through the same tool connection.
Use focused prompts for updates
AI assistants often make broader edits when a request is vague.
Instead of:
Make the page better.
Prefer:
Improve only the pricing section copy.
Do not change HTML structure outside that section.
Do not alter navigation, form fields, JavaScript, or global CSS.
Show the diff in plain language before publishing.
This makes the intended scope explicit.
For public pages, combine that prompt discipline with version history so a previous working release remains recoverable.
Troubleshooting: the connector does not appear
Check the following:
- Claude Desktop is signed in to the expected account.
- Custom connectors are available for that account or organization.
- On Team or Enterprise, an owner has allowed or added the connector.
- The connector was added under Customize → Connectors.
- The connector is enabled in the current conversation.
If you recently changed connector settings, remove and re-add the connector rather than assuming the existing configuration updated automatically.
Troubleshooting: authorization opens but does not complete
Verify that:
- you are signing in to the intended Deplion account;
- the browser is allowed to return to the authorization flow;
- cookies required for the sign-in session are available;
- the Deplion authorization page is not open in a different browser profile than the one where you started the flow.
Then retry the connector authorization from Claude Desktop.
Troubleshooting: Claude can see Deplion but does not use it
Tool availability and tool usage are separate things.
Be explicit:
Use the Deplion connector for this task.
For sensitive actions, ask Claude to stop before publication:
Use Deplion to update the project files, but do not publish until I review the result.
This creates a useful approval point in the conversation.
Troubleshooting: Claude edited more than requested
Do not ask the assistant to recreate the previous state from chat memory if a known-good published version already exists.
Use the project's version history and restore the earlier version, then retry the edit with a narrower instruction.
A practical recovery prompt is:
Restore the last working Deplion version.
Then change only the text inside the hero heading.
Do not modify any other file content.
The important part is that the rollback comes from a stored version rather than reconstruction from conversation context.
Security checks before publication
Before publishing a site created or edited by an AI assistant, ask Claude to inspect the files for:
- API keys;
- access tokens;
- private URLs;
- credentials;
- personal data accidentally copied from the conversation;
- third-party scripts you did not request;
- forms sending data to an unexpected destination.
Client-side HTML and JavaScript are visible to visitors. Treat anything in those files as public.
Final verification checklist
After connecting Claude Desktop to Deplion:
- Deplion appears under Claude connectors.
- The connector is authorized with the correct Deplion account.
- It is enabled in the current conversation.
- Claude can perform a read-only project request.
- A small test project can be created.
- You can review changes before publication.
- A published test version opens correctly.
- You know how to restore an earlier version before making production edits.
Once these checks pass, Claude Desktop can treat Deplion as part of the normal website workflow: Claude generates and edits the files, while Deplion manages projects, publication, forms, domains, and version recovery through MCP.