[Docs]: Provide full VS Code information for Github Copilot

[maximejobin]

📝 What type of documentation issue is this?

📋 Missing documentation for existing feature

🎯 What's the issue?

The screenshot and 2 links provided are not enough.

I came here: https://github.com/Teamwork/mcp/blob/main/usage.md#-vscode-github-copilot-chat-mcp

I was able to create the MCP.json file as expected. Then it asks to connect and asks for a client_id and client_secret.

I was able to go to /developer in my Teamwork account and create an app with these 2 informations and I entered them in the popup in VS Code. Then, it redirects me to mcp.ai.teamwork.com for authentication... then it fails.

Unfortunately, there is no specific steps in your documentation to know if I'm doing the right thing or not. Can you adjust the documentation with all steps as I'm unable to authenticate. I'm not sure about the part where I created a Teamwork app with client ID and secret... but it seems like I do not have a choice to provide these infos in VS Code.

Clarification on all the steps needed would help!

📍 Where is this issue?

https://github.com/Teamwork/mcp/blob/main/usage.md#-vscode-github-copilot-chat-mcp

📄 Current content (if applicable)

✨ Suggested improvement

Add all steps to be able to make it work in VS Code with Github Copilot

📝 Proposed content (optional)

👥 Who is this for?

🚀 Beginners - new to the MCP server

🎯 What would make this better?

• More code examples
• Step-by-step instructions
• Visual diagrams or screenshots
• Common pitfalls and how to avoid them
• Performance tips and best practices
• Error handling examples
• Real-world use case examples
• Links to related Teamwork API docs

🔍 Additional context

My MCP.json file :

{
  "inputs": [
    {
      "id": "tw-mcp-token",
      "type": "promptString",
      "description": "Teamwork Bearer token"
    }
  ],
  "servers": {
    "Teamwork.com": {
      "url": "https://mcp.ai.teamwork.com/",
    "type": "http",
      "headers": {
        "Authorization": "Bearer ${input:tw-mcp-token}"
      }
    }
  }
}

🙋 Would you like to help improve this?

• Yes, I can write the improved documentation
• Yes, I can provide feedback on drafts
• Yes, I can help test examples/tutorials
• I'd prefer the maintainers handle this

[rafaeljusto]

Thanks for raising this gap in our documentation Maxime. 🙂 I will work on it later this week. We may be able to simplify it now that we support the OAuth 2.0 Dynamic Client Registration Protocol for some vendors.

[maximejobin]

If it helps, I'm trying to do 2 things:

1. Connect to the MCP through VS Code (this ticket)
2. Connect to the MCP though Msty

Also, I was unable to generate a token using the "command line" :

It opens the browser where I see a 3-step process for half a second and it redirects me to login. I pick SSO (Google), click on my user and then...

I get this:

I do think we had a similar problem in the past for something else because we use a custom domain. That being said, I can't remember what the issue was and if this problem is because of our account or if it's a bug in your implementation.

Do not hesitate to tell me to contact support. I just don't know if it's a bug, a lack of documentation or something I misunderstood.

Thank you in advance!

[maximejobin]

I almost made it by editing my mcp.json to:

{
  "servers": {
    "Teamwork.com": {
      "url": "https://mcp.ai.teamwork.com/",
    "type": "http"
    }
  }
}

I was redirected to Teamwork login, I used my Google sign-on... but was redirected to VS Code with the message:

I tried to login to Teamwork using the same method and it worked. I don't understand why it works to login in Projects but not to connect MCP in Github.

I'll wait for your instructions!

[rafaeljusto]

Hey @maximejobin , sorry for the delay. I've changed the backend to allow OAuth 2.0 DCR for VSCode, so it should be much simpler to set up now. Please check the updated example config file:

mcp/.vscode/mcp.json

Lines 1 to 8 in c849df6

	{
	"servers": {
	"Teamwork": {
	"type": "http",
	"url": "https://mcp.ai.teamwork.com/"
	}
	}
	}

I will investigate the issue with the get-bearer-token CLI.

[maximejobin]

Hello @rafaeljusto ! It's basically what I did here:
#122 (comment)

I then took your exact code and still get the "We did not find any Teamwork account associated with this Google account.".

I tried to connect with ChatGPT and it works using OAuth.

I can't understand the difference and why it's not working. I do think the problem is from Teamworks' server as I'm able to complete all steps but Teamwork cannot match my Google account with our Teamwork account.

[maximejobin]

I asked a colleague to redo all my steps and it worked on his setup.

I'm pretty sure there is a problem with my Teamwork user or Teamwork account. Do you suggest I open a ticket? I do not think the problem is with the documentation or this project anymore... but it's linked to my account.

Thank you in advance!

[rafaeljusto]

It's basically what I did here

Ah yeah, sorry. I should have clarified. I've enabled a configuration today in the backend to allow your configuration to work without the extra hassle of generating applications in the developer portal. Now you won't need to provide the client ID since it will automatically generate that for you.

I'm pretty sure there is a problem with my Teamwork user or Teamwork account. Do you suggest I open a ticket? I do not think the problem is with the documentation or this project anymore... but it's linked to my account.

No need to open a ticket, this is too technical, and the support will end up asking me 😄 Could you provide the Teamwork URL (installation) and the e-mail account you are using to log in? You can send these details to rafael.justo@teamwork.com. I will try to analyse the logs to understand why it's failing for you.

[rafaeljusto]

I will investigate the issue with the get-bearer-token CLI.

I couldn't find out why the tool is broken, so I raised this for one of the maintainers internally.

[maximejobin]

Email sent with my infos!