softwaremill / softwaremill/chimp

SSE auto ping

Open
#9 21 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
102
Forks
10
Avg merge
1d 2h
Merged PRs (30d)
16

Description

It's easy to lost connection between MCP server and agent. This issue is faced by many people who create MCP server.
One way to keep connection on server side is implemented heartbeat. Examples of how this was approached in different projects:

Scala Metals
https://github.com/scalameta/metals/blob/39146132ddf16e827e3792c38eef0435b2a5e2f3/metals/src/main/scala/scala/meta/internal/metals/mcp/MetalsMcpServer.scala#L105

Rust SDK
https://github.com/modelcontextprotocol/rust-sdk/pull/74

I think it would be useful for people implementing MCP server to have some example how to do it with chimp (or even better to have some convenient abstraction).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Scala Metals MCP server implementation linked in the issue, especially MetalsMcpServer.scala around line 105, and compare it with the Rust SDK pull request. Determine whether chimp should provide an SSE heartbeat example or a reusable abstraction; done means a documented, usable approach for maintaining MCP server connections.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.