<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MCP Server on Raffle Documentation</title>
    <link>https://docs.raffle.ai/mcp/</link>
    <description>Recent content in MCP Server on Raffle Documentation</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://docs.raffle.ai/mcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude.ai</title>
      <link>https://docs.raffle.ai/mcp/claude-ai/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.raffle.ai/mcp/claude-ai/</guid>
      <description>Claude.ai supports remote MCP servers as connectors. Once added, you can activate the Raffle search tool in any conversation.&#xA;Personal plans (Pro and Max) Go to Customize &amp;gt; Connectors in Claude.ai settings. Click + and select Add custom connector. Enter a name (e.g. &amp;ldquo;Raffle&amp;rdquo;) and your MCP URL. Optionally click Advanced settings to add OAuth credentials. Click Add. Team and Enterprise plans Connectors are added at the organisation level by an owner, then activated by individual members.</description>
    </item>
    <item>
      <title>ChatGPT</title>
      <link>https://docs.raffle.ai/mcp/chatgpt/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.raffle.ai/mcp/chatgpt/</guid>
      <description>ChatGPT supports MCP servers through MCP apps in the desktop application. A ChatGPT Plus or Pro subscription is required.&#xA;Steps Open the ChatGPT desktop app and go to Settings. Navigate to Connected apps (or Features, depending on your version). Enable Developer mode if prompted. Under MCP Servers, click Add server. Enter your MCP URL and a name for the server. Save the configuration. The Raffle search tool will then be available to ChatGPT during conversations.</description>
    </item>
    <item>
      <title>MS Copilot</title>
      <link>https://docs.raffle.ai/mcp/ms-copilot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.raffle.ai/mcp/ms-copilot/</guid>
      <description>Microsoft Copilot Studio lets you connect MCP servers to your agents using a built-in wizard. The Raffle MCP server uses the Streamable HTTP transport.&#xA;Steps Open your agent in Copilot Studio and go to the Tools page. Click Add a tool → New tool → Model Context Protocol. Fill in Server name and Server description — the description helps the agent decide when to call the tool, so be specific (you can reuse your tool description).</description>
    </item>
    <item>
      <title>OpenWebUI</title>
      <link>https://docs.raffle.ai/mcp/openwebui/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.raffle.ai/mcp/openwebui/</guid>
      <description>Open WebUI supports MCP servers from version 0.6.31 onwards.&#xA;Steps Go to Admin Settings → External Tools. Click + (Add Server). Set Type to MCP (Streamable HTTP) — not OpenAPI. Enter your MCP URL in the Server URL field. Set authentication to None. Click Save. Restart Open WebUI if prompted. Docker environments Note If your Open WebUI instance runs in Docker and the MCP server is on the host machine, use http://host.</description>
    </item>
    <item>
      <title>Other clients</title>
      <link>https://docs.raffle.ai/mcp/other/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.raffle.ai/mcp/other/</guid>
      <description>The Raffle MCP server works with any client that supports remote MCP servers over Streamable HTTP transport.&#xA;General setup The configuration details vary by client, but the core steps are the same:&#xA;In your client&amp;rsquo;s MCP or tools settings, add a new server. Set the server URL to your MCP URL (https://mcp.raffle.ai/experimental/{UID}/mcp). Set the transport type to Streamable HTTP (also called HTTP+SSE in older clients — prefer Streamable HTTP where available).</description>
    </item>
  </channel>
</rss>
