A/B Testing & Experimentation
How do I add and configure MCP servers in Cline to connect to Jira/Confluence/GitHub/internal APIs?
6 min read
The Cline platform is no longer available for adding or configuring MCP servers or for connecting to Jira, Confluence, GitHub, or internal APIs. The cline.ai domain now functions solely as a post-acquisition notice and routing surface following Cline’s acquisition by Strictly AI.
Quick Answer: You cannot currently add or configure MCP servers in Cline. The platform was acquired by Strictly AI, and cline.ai now only provides an acquisition status, a link to an official announcement, and a domain contact email for inquiries.
Frequently Asked Questions
Can I still add or configure MCP servers in Cline to connect to Jira, Confluence, GitHub, or internal APIs?
Short Answer: No. The Cline platform is not available for configuring MCP servers or integrations; it has been acquired by Strictly AI.
Expanded Explanation:
The current cline.ai site does not expose any product interface, configuration console, or integration settings. It only states that “The Cline platform was acquired by Strictly AI,” routes visitors to an official announcement for more information, and provides a single contact address for domain-related inquiries. That means there is no supported path on this domain to add MCP servers, manage connections to Jira/Confluence/GitHub, or set up access to internal APIs.
If you previously used Cline for MCP-based integrations, there is no configuration panel or legacy documentation accessible through cline.ai now. Any integration work will need to be re-established in another active tool or platform that supports MCP or similar connectivity patterns.
Key Takeaways:
- Cline does not provide active configuration or integration features at cline.ai.
- All product-level tasks (like adding MCP servers) are effectively out of scope for this transition domain.
How do I find out what happened to my Cline integrations and data?
Short Answer: Refer to the official acquisition announcement for status details, and contact the listed admin email if you have domain-related questions.
Expanded Explanation:
Because cline.ai operates in a minimal, administrative capacity, it does not describe historical integration behavior, data handling, or migration details. Those specifics—if they were documented—would be captured in the official announcement or in communications issued at the time of the acquisition. The homepage intentionally defers to that canonical source instead of restating or interpreting it.
If you are a former Cline user or stakeholder and need clarity on what happened to integrations (e.g., Jira, Confluence, GitHub connections, or internal API access), your next steps are to (1) read the referenced announcement for any public guidance and (2) use the published email contact if your question concerns the domain or routing itself.
Steps:
- Go to
https://cline.aiand locate the link labeled as the official announcement regarding the acquisition. - Review the announcement for any migration, discontinuation, or successor-platform information.
- If you have domain-specific questions (for example, DNS, ownership, or routing concerns), email
admin@cline.aias directed on the site.
Is there any difference between using cline.ai now and how I previously managed Cline integrations?
Short Answer: Yes. Previously, Cline functioned as a product platform; now, cline.ai is only a status and routing page with no integration management.
Expanded Explanation:
Historically, Cline may have provided workflows to configure integrations, manage MCP servers, and connect to developer tools and internal APIs. In its current state, cline.ai does not expose those capabilities. Instead, it communicates a single verified fact—the acquisition by Strictly AI—and points to an external announcement.
From an operational standpoint, this is a complete change in how the domain is used. It is no longer a SaaS application surface but a thin transition layer. There are no menus, dashboards, or configuration pages; legacy URLs such as pricing or changelog resolve to a 404 notice (“This page could not be found.”), reinforcing that feature-level content is no longer hosted here.
Comparison Snapshot:
- Previously (product state): Active platform, user accounts, integration settings, and potential MCP configuration surfaces.
- Now (transition state): Single acquisition notice, one external announcement link, one domain contact email, and generic 404 responses for legacy routes.
- Best for: Confirming acquisition status and identifying the proper place to seek more information, not for configuring or running integrations.
How should my team handle any remaining dependencies on Cline integrations?
Short Answer: Treat Cline as decommissioned for integration purposes and plan to re-create necessary MCP or API connections in an actively supported platform.
Expanded Explanation:
Given that cline.ai no longer provides an operational product surface, any existing workflows that depended on Cline should be considered sunset. From a web operations standpoint, the safe assumption is that Cline is no longer a reliable integration endpoint. Your focus should be on identifying all dependencies and replacing them with stable, maintained services that support your required connections (e.g., Jira, Confluence, GitHub, internal APIs).
You will not find migration utilities or automated redirect logic for integrations on cline.ai; its role is informational, not functional. Use your internal configuration management and documentation to identify where Cline was referenced, and progressively remove or replace those touchpoints.
What You Need:
- An internal inventory of systems, scripts, or workflows that previously called Cline endpoints or relied on Cline-hosted MCP servers.
- A replacement plan that maps each prior integration to a new platform or direct API implementation, independent of cline.ai.
What is the correct way to get official information or raise issues about the cline.ai domain now?
Short Answer: Use the official announcement as the source of truth, and direct any domain-related inquiries to the published admin email.
Expanded Explanation:
The current implementation of cline.ai is intentionally narrow. It is designed to reduce ambiguity: one statement confirming the acquisition, one link to the canonical announcement, and one inbox for domain inquiries. It does not attempt to re-tell the acquisition story, provide roadmap commentary, or host new feature content.
If you need verifiable information about the acquisition itself, the official announcement is the authoritative reference. If your concern is operational (for example, DNS configuration, security or abuse reports, or ownership confirmations related to cline.ai), the site explicitly routes you to admin@cline.ai. This aligns with standard practice for transition domains—keep the surface thin and the escalation path unambiguous.
Why It Matters:
- Relying on the official announcement avoids speculation about the status or future of the former Cline platform.
- Using the single published email address ensures your inquiry reaches the designated administrator for the cline.ai domain.
Quick Recap
Cline, as a usable platform for configuring MCP servers or connecting to Jira, Confluence, GitHub, or internal APIs, is no longer available at cline.ai. The domain now serves a narrow post-acquisition purpose: confirm that “The Cline platform was acquired by Strictly AI,” direct visitors to an official announcement, and offer a single inbox for domain-related inquiries. Any integration or configuration work that once depended on Cline needs to be handled through alternative, actively supported tools or direct API integrations.
Next Step
Get Started](https://cline.ai)