SShortSingh.
Back to feed

Exposing a local MCP server: tunnels are easy, access control is the hard part

0
·10 views

A DEV Community article argues that making a local MCP server reachable is the simple step, while deciding who can call it and revoking access without redeploying takes most of the effort. It explains that stdio transport only works for one person on one machine, so remote use needs HTTP or SSE transport. The author outlines four needs: a stable address, transport, authentication, and revocation. Five approaches are compared, including ngrok, Cloudflare Tunnel with Access, exposing a port directly, and moving the server to a VPS. The piece ends by describing an outbound-relay model in which the server connects out to a relay and nothing listens on the local machine.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

llms.txt Format Explained: Structure, Template and Common Errors

llms.txt is a Markdown file served at /llms.txt that gives AI tools a short, curated list of a site's key pages. It is a community proposal from llmstxt.org first written in 2024, and it is optional rather than an official standard. The proposal defines a fixed order: a required H1 with the site name, an optional blockquote summary, optional detail sections, and H2 link lists, with an optional section for secondary links. The article provides an example template and explains how to publish the file and confirm it returns a 200 status with a non-HTML content type. It also notes that the author's own auditor checks only format compliance, and that the crawler documentation it reviewed treats robots.txt, not llms.txt, as the control for AI access.

0
ProgrammingDEV Community ·

Repositório de exemplos da série IPFS com Nabu: como rodar os programas

O post final da série sobre IPFS com o Nabu executa os programas do módulo examples/ do repositório, em vez de abrir o nó por dentro como os anteriores. Cada programa de linha de comando faz uma tarefa, usando um nó compartilhado que guarda blocos e registros IPNS apenas na memória. Os scripts em examples/scripts/ sobem os processos e verificam a saída, com variantes para Windows (.ps1) e shell (.sh). Há opções para pular a API ou usar portas efêmeras, e os logs ficam em target/example-tests/.

0
ProgrammingDEV Community ·

HTTP entre pares via libp2p: pedidos sem endereço público

A série sobre IPFS com o Nabu mostra como levar pedidos HTTP a outro par sem que ele tenha endereço público na internet. A proposta transporta a requisição e a resposta HTTP dentro de um stream libp2p, usando o PeerId para localizar o destino, o que evita abrir portas no roteador ou alugar um servidor intermediário. Um proxy local permite que um cliente HTTP comum, em 127.0.0.1, acesse o par remoto sem conhecer o PeerId, enquanto a DHT resolve o endereço quando necessário. O protocolo /http é registrado na aplicação e tem limite de corpo de 8 MiB por mensagem, marcado no código como solução temporária. O artigo descreve a implementação em Java e o funcionamento do handler no processo Nabu.

0
ProgrammingDEV Community ·

Student Recounts Juggling Full-Time Work, Study and Long Commutes

A university student describes spending their first year balancing a part-time job, private tutoring, and a three-hour daily commute. They reflect that they had been surviving rather than running a sustainable system. Their most painful moment was missing a top grade by a razor-thin margin, which they say still stings. Despite the strain, they chose to keep going, and they say that persistence has shaped them in lasting ways. They are now starting their final year with fewer distractions, though they admit they have no neat conclusion about whether the sacrifices were worth it.