Skip to content

Modify http config export type from http to streamable-http#2255

Merged
crivetimihai merged 1 commit intoIBM:mainfrom
stephanriley-ibm:issue-2254
Jan 21, 2026
Merged

Modify http config export type from http to streamable-http#2255
crivetimihai merged 1 commit intoIBM:mainfrom
stephanriley-ibm:issue-2254

Conversation

@stephanriley-ibm
Copy link
Copy Markdown
Contributor

🐛 Bug-fix PR

Before opening this PR please:

  1. make lint - passes ruff, mypy, pylint
  2. make test - all unit + integration tests green
  3. make coverage - ≥ 90 %
  4. make docker docker-run-ssl or make podman podman-run-ssl
  5. Update relevant documentation.
  6. Tested with sqlite and postgres + redis.
  7. Manual regression no longer fails. Ensure the UI and /version work correctly.

📌 Summary

Changes the "type" for the HTTP config export from "http" to "streamable-http" as that is what agents expect.

🔁 Reproduction Steps

#2254

Log in to Context Forge UI
Go to Virtual Servers page
If you don't have a Virtual Server created, you will need to create one
Select the "Export Config" button for one of your Virtual Servers.
Choose the option for "HTTP (REST clients)"
See the configuration JSON contain the setting "type": "http"

🐞 Root Cause

The type was set incorrectly in the static/admin.js generateConfig http case.

💡 Fix Description

Changed type from "http" to "streamable-http"

🧪 Verification

Check Command Status
Lint suite make lint
Unit tests make test
Coverage ≥ 90 % make coverage
Manual regression no longer fails steps / screenshots

✅ Checklist

  • Code formatted (make black isort pre-commit)
  • No secrets/credentials committed

@crivetimihai crivetimihai merged commit e06f3ac into IBM:main Jan 21, 2026
51 checks passed
@stephanriley-ibm stephanriley-ibm deleted the issue-2254 branch January 21, 2026 21:31
010gvr pushed a commit to 010gvr/mcp-context-forge that referenced this pull request Jan 23, 2026
kcostell06 pushed a commit to kcostell06/mcp-context-forge that referenced this pull request Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants