feat: add new specification regarding json response streamable http

[jirispilka]

Add server and example client that support HTTP JSON response

modelcontextprotocol sdk points to a for of the official repo

    "@modelcontextprotocol/sdk": "github:jirispilka/mcp-typescript-sdk#fix/add-src-dir",

[jirispilka]

@MQ37 Any idea how to fix this?

I've encountered lint issue in CI that I was not able to fix:

/home/runner/work/actors-mcp-server/actors-mcp-server/src/tools/mcp-apify-client.ts
Error:   1:1  error  Too many blank lines at the beginning of file. Max of 0 allowed  no-multiple-empty-lines
✖ 1 problem (1 error, 0 warnings)
  1 error and 0 warnings potentially fixable with the `--fix` option.
Error: Process completed with exit code 1.

But this is working at my local. I change the workflow to npm run lint:fix to "fix it"

[Copilot]

Copilot reviewed 22 out of 25 changed files in this pull request and generated 2 comments.

Files not reviewed (3)

• .nvmrc: Language not supported
• package.json: Language not supported
• src/tsconfig.json: Language not supported

[MQ37]

@MQ37 Any idea how to fix this?

I've encountered lint issue in CI that I was not able to fix:

/home/runner/work/actors-mcp-server/actors-mcp-server/src/tools/mcp-apify-client.ts
Error:   1:1  error  Too many blank lines at the beginning of file. Max of 0 allowed  no-multiple-empty-lines
✖ 1 problem (1 error, 0 warnings)
  1 error and 0 warnings potentially fixable with the `--fix` option.
Error: Process completed with exit code 1.

But this is working at my local. I change the workflow to npm run lint:fix to "fix it"

that is weird, also works for me locally - even those previous failing commits 🤷 Let's ignore that for now, I think we should address linter and formatter in the future once all of this is merged and deployed.

[MQ37]

we should probably use the express error handler, otherwise good work and LGTM 👍