SShortSingh.
Back to feed

MCP servers can now connect via OAuth 2.1, removing the need for manual API keys

0
·2 views

Panth, who leads software at Oizom, describes an open-source ticket tracker that lets users add its MCP server to Claude with one URL and a consent click. The design uses OAuth 2.1 with PKCE, dynamic client registration, and protected-resource metadata, as the MCP authorization spec expects. Users can review and revoke access in their account settings, and API keys remain available for headless setups without a person present. The flow relies on discovery documents so a client can follow a 401 response through to a working token. Access tokens last one hour and refresh tokens 30 days, with tokens stored only as hashes.

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 ·

Why the First Two Weeks of an AI Deployment Decide Its Outcome

An engineer embedded with a customer during the opening stretch of a deployment works to replace assumptions with facts before building anything. The brief written in a meeting room often describes a proxy rather than the real problem, which becomes clear only after observing daily operations. The article outlines five principles: focus on the actual problem rather than a stated tool, request data and system access immediately, examine raw unfiltered data before designing, select a small but meaningful first workflow, and identify every stakeholder who could block the work. Skipping this phase, it argues, results in building the wrong solution efficiently. Early discovery turns potential delays into useful signals about how the deployment will run.

0
ProgrammingDEV Community ·

Semurg answers 4-hop query on 1.8-billion-edge graph in 1.41 s; Neo4j and FalkorDB fail to finish

A benchmark used SNAP's com-Friendster graph, with 65.6 million people and 1.8 billion relationships, under a 12 GB memory limit for every engine. Semurg answered a 4-hop query about one person's network in a median of 1.41 seconds. Neo4j loaded the graph but had not answered that query when its 2,345-second time budget ran out. FalkorDB exhausted its 12 GB memory while loading and never reached a query. Semurg also completed walks from two hops up to 131,072 hops, with run times levelling off at about 6.7 seconds beyond 16 hops because the graph is small-world. ArcadeDB, ArangoDB and SurrealDB were not fairly measured or have no result in this run and are slated for the next one.

0
ProgrammingHacker News ·

Microagi Launches Project Aimed at Accelerating Embodied AGI Development

Microagi has published a website describing its work on accelerating embodied artificial general intelligence. The item surfaced on Hacker News, where it gathered a few points and no discussion comments at the time of posting. The source material provides only the project name, a link to the company's site, and basic community engagement metrics. Specific technical details, timelines, funding, or research results are not included in the available text.

0
ProgrammingDEV Community ·

Claude Code Can Now Run on Local or Cloud Models via Ollama on Windows

A developer has published a guide showing how to run the Claude Code terminal coding agent with models served by Ollama instead of Anthropic's accounts. The setup requires Node.js for installing Claude Code, the Ollama app on Windows, and a local model chosen from Ollama's list, such as the small qwen3.5:0.8b used in the example. Local models keep prompts and code on the user's machine but depend heavily on hardware and model size. For more capable models, Ollama's cloud options can be used after signing in, though these send prompts to Ollama's servers and have usage caps.