mcp with obsidian not working

[Teemops2806]

Hello, I am not a dev, bit try to get oj running on windows with mcp to obsidian and later to home assistant.
mcp config in config.toml is fine so far, but it seems, as if the url or the token are not handed correctly to obsidian mcp server (mcp connector plugin) although everything is set correctly.
Could there be a bug in mcp config or handshake with the mcp server?
First Analysis seem to show that only http://117.0.0.1: are given, not the port or "/mcp".

I am trying now for four days. No chance till now. Could anyone give some hint how to solve this?
Send you best regards from Germany,
Frank

[hosanxiv]

The current implementation does not strip the port or path from the configured URL: it passes the full url value into StreamableHTTPTransport, which POSTs directly to that value (loader, transport).

The important part is that servers must be a JSON-encoded string inside TOML, not a TOML table/array. A minimal authenticated configuration is:

[tools.mcp]
enabled = true
servers = '[{"name":"obsidian","url":"http://127.0.0.1:YOUR_PORT/mcp","token":"YOUR_TOKEN"}]'

A few checks:

1. Make sure the address is 127.0.0.1, not 117.0.0.1.
2. Keep the port and /mcp inside the quoted JSON url value.
3. Restart OpenJarvis after editing the config.
4. From the same Windows environment, test that the exact URL is listening. If Obsidian or OpenJarvis is inside a container/VM, 127.0.0.1 points to that container/VM, not the Windows host.
5. The token field becomes Authorization: Bearer <token> (header construction).

The project now has the same format documented in its external MCP guide. If the exact configuration above still produces a shortened URL, please paste the redacted [tools.mcp] block and the warning line; that would distinguish a config parsing problem from the Obsidian plugin binding only to a different interface.

[Teemops2806]

Hi there, thanks for answering! …but, this is what I still get: WARNING openjarvis.mcp.loader: Failed to discover MCP tools from 'obsidian': MCP server at http://127.0.0.1:27123 returned HTTP 401 And this is what I configured in config.toml: # TOOLS # ---------------------------------------------------------------------------- [tools] enabled = [ "code_interpreter", "web_search", "file_read", "file_write", "shell_exec", "memory_store", "memory_retrieve", "memory_search", "mcp" ] [tools.mcp] enabled = true servers = '[{"name":"obsidian","url": "http://127.0.0.1:27123/mcp","token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}]' [tools.file_write] allowed_dirs = ["D:\\second brain"] It still doesn’t work ☹ Any hints? I would really appreciate that. Trying to get this work – but doesn’t matter how – no success till now. Best regards! Frank Von: Hosan ***@***.***> Gesendet: Donnerstag, 16. Juli 2026 16:38 An: open-jarvis/OpenJarvis ***@***.***> Cc: Teemops2806 ***@***.***>; Author ***@***.***> Betreff: Re: [open-jarvis/OpenJarvis] mcp with obsidian not working (Discussion #633) The current implementation does not strip the port or path from the configured URL: it passes the full url value into StreamableHTTPTransport, which POSTs directly to that value (loader <https://github.com/open-jarvis/OpenJarvis/blob/8b59eb87e0b6006d898947647b042bba28e25ed4/src/openjarvis/mcp/loader.py#L83-L104> , transport <https://github.com/open-jarvis/OpenJarvis/blob/8b59eb87e0b6006d898947647b042bba28e25ed4/src/openjarvis/mcp/transport.py#L121-L180> ). The important part is that servers must be a JSON-encoded string inside TOML, not a TOML table/array. A minimal authenticated configuration is: [tools.mcp] enabled = true servers = '[{"name":"obsidian","url":"http://127.0.0.1:YOUR_PORT/mcp","token":"YOUR_TOKEN"}]' A few checks: 1. Make sure the address is 127.0.0.1, not 117.0.0.1. 2. Keep the port and /mcp inside the quoted JSON url value. 3. Restart OpenJarvis after editing the config. 4. From the same Windows environment, test that the exact URL is listening. If Obsidian or OpenJarvis is inside a container/VM, 127.0.0.1 points to that container/VM, not the Windows host. 5. The token field becomes Authorization: Bearer <token> (header construction <https://github.com/open-jarvis/OpenJarvis/blob/8b59eb87e0b6006d898947647b042bba28e25ed4/src/openjarvis/mcp/transport.py#L150-L168> ). The project now has the same format documented in its external MCP guide <https://github.com/open-jarvis/OpenJarvis/blob/8b59eb87e0b6006d898947647b042bba28e25ed4/docs/user-guide/mcp-external-servers.md#configuration> . If the exact configuration above still produces a shortened URL, please paste the redacted [tools.mcp] block and the warning line; that would distinguish a config parsing problem from the Obsidian plugin binding only to a different interface. — Reply to this email directly, view it on GitHub <#633?email_source=notifications&email_token=BGOJEKME4HAXSBETNO7YKS35FDSFXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYZDQMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17662811> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGOJEKMWVJUW6VPRG3AT74T5FDSFXAVCNFSNUABJKJSXA33TNF2G64TZHMYTCNJYGE4TQMRTGQ5UI2LTMN2XG43JN5XDWMJQGQYTENZUG2QXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BGOJEKL43Z4SZV35SKCOKA35FDSFXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYZDQMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/BGOJEKJBA6VATEI5W7JJM7L5FDSFXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGYZDQMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE> . Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

…

-- Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft. www.avast.com