Last updated 7 November 2026.
What is possible
The community plugin Local REST API with MCP by Adam Coddington includes an MCP server that runs inside Obsidian. Its README says the server uses the Streamable HTTP transport and needs an API key. AskWatch connects to MCP servers over Streamable HTTP, at an address you enter.
- The Mac has to be on. The plugin runs inside the desktop version of Obsidian, so Obsidian has to be open on the Mac with the plugin enabled, whichever route you use. The address in the steps below, 127.0.0.1, always means the computer you are on. That is why those steps work in AskWatch on the Mac where Obsidian runs, and not on an iPhone, iPad or Apple Watch. A second route through Tailscale can reach it from an iPhone or iPad.
- Tools for your notes. The plugin lists tools that read, search, create, change, move and delete notes, and that run Obsidian commands.
- Community software. The plugin is not made by Obsidian or by AskWatch. AskWatch has not tested it.
What you need
- AskWatch on a Mac, with the MCP Servers tab in its Settings.
- Obsidian on the same Mac with community plugins turned on. Obsidian runs community plugins only when Restricted mode is off. Read Obsidian's page on plugin security first: it says community plugins can access files on your computer.
- The plugin Local REST API with MCP, installed from Obsidian's community plugins and enabled. It is listed in Obsidian's plugin directory.
- The plugin's API key, shown in Obsidian under Settings → Local REST API.
Step by step
- In Obsidian, turn on community plugins, install Local REST API with MCP and enable it.
- In Obsidian open Settings → Local REST API. Copy the API key and switch on Enable HTTP server. The README names that switch as the way to use the plugin's plain HTTP address.
- In AskWatch on your Mac open Settings, then the MCP Servers tab, choose Add MCP Server and then Add by address.
- Enter any name under Server name. Under Server URL enter
http://127.0.0.1:27123/mcp/. Set Authentication to Bearer Token and paste the API key into the Bearer Token field. Then choose Add and Test Server. - Because the address starts with http, AskWatch first shows the warning Unencrypted MCP connection. Read it, switch on I understand the risks and choose I understand — Continue.
- AskWatch then asks the server for its tools. Every tool found during this setup starts at Ask every time.
Names from Obsidian and from the plugin are written in English, as the plugin's README writes them.
The https address
The plugin also offers https://127.0.0.1:27124/mcp/. Its certificate comes from a certificate authority that the plugin creates itself, and the README says a client must trust that authority. AskWatch's code for MCP connections contains no exception for certificates that macOS does not trust. Use the http address, unless you have made macOS trust the plugin's certificate authority. We have not tried the https address.
On an iPhone or iPad
The plugin listens only on the Mac itself unless you change its Binding host setting. For an iPhone or iPad the address has to reach the Mac over a network, so this is a second route and it takes more work. Every route in the table below is one that AskWatch has not tried. The commands and settings come from the products' own documentation.
When sync is on, AskWatch syncs the MCP servers you add, with their address, to your other devices. An address on your tailnet is the same on every device. The address 127.0.0.1 always means the device it is used on, so a server added on the Mac with that address does not reach Obsidian from an iPhone.
What AskWatch can send decides which routes work. The Add by address form offers None, Bearer Token and OAuth Sign-In. It has no field for extra request headers.
Every route we found
Routes that other devices can use to reach the plugin on the Mac, from the documentation of the products named, and whether AskWatch can use them today.
| Route | iPhone and iPad | Who can reach the vault tools | What you set up | Our view | Can AskWatch use it today |
|---|---|---|---|---|---|
The Mac only, at 127.0.0.1 (the steps above) | No | Programs on that Mac | The plugin and its HTTP server switch | The simplest route. No other device can connect. | Yes. AskWatch has not tried it. |
| Tailscale Serve (steps below) | Yes, with the Tailscale app signed in to the same tailnet | Devices in your tailnet that your Tailscale access rules allow | Tailscale on both devices, Enable HTTPS in the admin console, one command on the Mac | A private route. Keep the tools at Ask every time. | Yes, with an https address that ends in ts.net. AskWatch has not tried it. |
| Tailscale Funnel | Yes | Anyone on the internet | One command on the Mac | Not recommended. The plugin's API key would be the only protection for tools that can write and delete notes. | AskWatch would accept an https address, but we do not recommend this route and give no steps. |
| Cloudflare Tunnel alone, with a public hostname | Yes | Anyone on the internet who reaches the hostname | A domain on Cloudflare, cloudflared on the Mac, a public hostname for the plugin | Not recommended. The plugin's API key would be the only protection for tools that can write and delete notes. | AskWatch would accept an https address, but we do not recommend this route and give no steps. |
| Cloudflare Tunnel with Cloudflare Access and a service token | Yes | Only requests that carry the service token | A domain on Cloudflare, a tunnel, an Access application with a Service Auth policy, a service token | It would be private, but AskWatch cannot send the token. | No. It does not work today: the Add by address form and the MCP connection have no fields for the request headers CF-Access-Client-Id and CF-Access-Client-Secret. Support is planned. |
| Cloudflare Tunnel with Cloudflare Access and a login (Managed OAuth) | Yes | People that your Access policy allows | As in the row above, with Managed OAuth turned on for the Access application | It would be private, but we do not know that it works. | Not known. The plugin wants its own API key in the Authorization header and AskWatch sends one Authorization value, so we do not see how both could be sent. AskWatch has not tried it. |
| A Cloudflare private network, with the Cloudflare One Client on the iPhone or iPad | Yes, with the Cloudflare One Agent app | Devices enrolled in your Cloudflare Zero Trust organization | A Zero Trust organization, a connector and a route, the app on the device | Private in principle. | Not known. In the pages we read we did not find how such a route reaches a service that listens only on 127.0.0.1, so we give no steps. |
| The Mac's address on your home network | Yes, on the same network | Every device on that network | Set the plugin's Binding host to the Mac's address | Not recommended. The connection is plain http, and every device on the network can reach the plugin. | AskWatch accepts plain http to private addresses and shows its warning Unencrypted MCP connection. We give no steps. |
Steps for Tailscale Serve
Use these steps only if you accept that AskWatch has not tried them and that every device your Tailscale rules allow can reach the plugin.
- Install Tailscale on the Mac and on the iPhone or iPad and sign in to the same tailnet on both. On iOS the app asks to install a VPN configuration. Keep Tailscale connected on the iPhone or iPad while you use the tools.
- In the Tailscale admin console open the DNS page, turn on MagicDNS if it is off, and under HTTPS Certificates choose Enable HTTPS. Tailscale warns that your machine names and your tailnet name are then published on a public ledger of certificates, so do not enable it if a machine name is sensitive.
- In Obsidian check that Enable HTTP server is on, as in step 2 above. The plugin keeps listening on 127.0.0.1 only.
- In a terminal on the Mac run
tailscale serve --bg http://127.0.0.1:27123. Tailscale prints an address of the formhttps://device-name.tailnet-name.ts.net. Runtailscale serve statusto see it again andtailscale serve resetto switch serving off. - In AskWatch on the iPhone or iPad open Settings, then MCP Servers, then Manage MCP Servers. Choose Add MCP Server and then Add by address.
- Enter any name under Server name. Under Server URL enter the address from the previous command with
/mcp/at the end, for examplehttps://device-name.tailnet-name.ts.net/mcp/. Set Authentication to Bearer Token, paste the plugin's API key and choose Add and Test Server. The address starts with https, so AskWatch shows no warning about an unencrypted connection.
Tailscale gets the certificate from Let's Encrypt, a public certificate authority, so you do not have to trust a certificate by hand. We have not checked this on a device.
Do not use tailscale funnel for this. Tailscale describes tailscale serve as sharing a service within your tailnet and tailscale funnel as sharing it over the internet, open to everyone.
Tailscale's access rules apply to Serve like to any other service, and a device shared into your tailnet can reach it too. The plugin's own API key is still needed. Keep the tools at Ask every time.
Before you let it work on your notes
- The plugin's tools can write, move and delete notes and run any Obsidian command. In AskWatch each tool can be set to Off, Ask every time or Run without asking.
- Leave the tools at Ask every time. For a tool that the server does not mark as read-only, AskWatch shows a warning before it accepts Run without asking.
- What a tool returns becomes part of the conversation, so it goes to the AI provider you chose. The plugin's README says a result usually goes straight into the model's context.
- According to the README, the plugin gates access with the API key. Keep the key private and do not make the plugin's port reachable from the internet.
- AskWatch saves the key in the Keychain, as an item that can sync to your other devices through iCloud Keychain.
If it does not work
- Check that Obsidian is open, that the plugin is enabled, that Enable HTTP server is on, and that the address is exactly
http://127.0.0.1:27123/mcp/, with the port and the final slash. - Check that you pasted the plugin's current API key. According to the README, after 10 wrong keys within a minute the plugin refuses further wrong keys until that minute is over.
- Another community option is obsidian-mcp-server by cyanheads, which works through the same plugin. Its README says it supports STDIO or Streamable HTTP, runs as STDIO by default, and in HTTP mode (
MCP_TRANSPORT_TYPE=http) listens athttp://127.0.0.1:3010/mcp. AskWatch can only use a server's HTTP mode. The plugin's README says third-party servers are no longer necessary. We have not tried this one either. - We cannot promise that this route works, and we cannot fix a third-party plugin. Report a problem with the plugin to its issue tracker.
What we have not checked
- Nobody at AskWatch has connected AskWatch to this plugin. We do not know whether Add and Test Server succeeds against it.
- On paper the two sides share protocol revisions: AskWatch speaks MCP revisions 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26, and the plugin's README says it serves 2026-07-28 and 2024-10-07 through 2025-11-25. We have not tried it.
- We have not tried the https address, or any other Obsidian plugin or server.
- The plugin and Obsidian can change. This page follows the README of plugin version 5.5.2, published on 17 October 2026, as read on 7 November 2026.
- We have not tried any route for the iPhone or iPad, neither Tailscale nor one of the others in the table. The commands and settings come from the documentation of Tailscale and Cloudflare as read on 7 November 2026.
Third-party notice
Obsidian, Tailscale and Cloudflare are third-party products. AskWatch is not affiliated with or endorsed by Obsidian, Tailscale or Cloudflare. Their names and marks belong to their respective owners.
Sources
All read on 7 November 2026.
- Local REST API with MCP: README on GitHub
- Obsidian: Plugin security
- Obsidian plugin directory: Local REST API with MCP
- cyanheads/obsidian-mcp-server: README on GitHub
- RFC 1122, section 3.2.1.3: the 127 loopback addresses
- Tailscale: the tailscale serve command
- Tailscale: Tailscale Serve
- Tailscale: the tailscale funnel command
- Tailscale: Enabling HTTPS
- Tailscale: Install Tailscale on iOS
- Cloudflare: Tunnel for public applications
- Cloudflare: Universal SSL certificates
- Cloudflare: Access service tokens
- Cloudflare: Access policies
- Cloudflare: Managed OAuth
- Cloudflare: Private networks
- Cloudflare: Cloudflare One Client downloads
- Local REST API with MCP: source file with the default binding host