# \[MCP\] Perplexity connector

**URL:** <https://community.homey.app/t/mcp-perplexity-connector/144968>\
**Category:** Questions & Help\
**Created:** [November 5, 2025, 9:21am UTC](https://community.homey.app/t/mcp-perplexity-connector/144968 "2025-11-05T09:21:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rvanlaak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rvanlaak/32/108826_2.png) [@rvanlaak](https://community.homey.app/u/rvanlaak)\
**Post date:** [November 5, 2025, 9:21am UTC](https://community.homey.app/t/mcp-perplexity-connector/144968/1 "2025-11-05T09:21:21Z")

</div>

Exciting news! [Introducing the Homey MCP Server – News | Homey](https://homey.app/en-us/news/introducing-the-homey-mcp-server/)

When trying to add the Homey MCP server to Perplexity; which config should I use?

The environment I’m at is the MacOS Perplexity app, with the helper app installed.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/0/902a598f451dab84f4281f0d53c341f70a2acc92.png)

The ‘Advanced’ section allows defining the config as json.

Ref: [https://www.perplexity.ai/help-center/en/articles/11502712-local-and-remote-mcps-for-perplexity#h\_2c7ef0caea](https://www.perplexity.ai/help-center/en/articles/11502712-local-and-remote-mcps-for-perplexity#h_2c7ef0caea)

---

<div class="post-metadata">

**Author:** ![Xander\_Hoose](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/xander_hoose/32/131829_2.png) [@Xander\_Hoose](https://community.homey.app/u/Xander_Hoose)\
**Post date:** [November 5, 2025, 11:09am UTC](https://community.homey.app/t/mcp-perplexity-connector/144968/2 "2025-11-05T11:09:28Z")

</div>

Homey heeft gekozen voor RESTful HTTP API (REST/OAuth) in plaats van de gangbare STDIO of SSE calls voor MCP. Deze wordt vooralsnog niet door Perplexity (en veel andere clients) ondersteund.

> If the MCP server only supports REST API calls with OAuth (rather than SSE or stdio), it may not be directly compatible with Perplexity’s current MCP integration, unless explicit support for REST/OAuth bridges is provided.

---

<div class="post-metadata">

**Author:** ![rvanlaak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rvanlaak/32/108826_2.png) [@rvanlaak](https://community.homey.app/u/rvanlaak)\
**Post date:** [November 6, 2025, 4:04pm UTC](https://community.homey.app/t/mcp-perplexity-connector/144968/3 "2025-11-06T16:04:52Z")

</div>

I’d imagine that over time StreamableHTTP would take over: [MCP Transport Protocols: stdio vs SSE vs StreamableHTTP | MCPcat](https://mcpcat.io/guides/comparing-stdio-sse-streamablehttp/)