No per-provider instructions for getting a client ID and secret
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 10
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
Every provider hands out client IDs and secrets through a completely different flow. GitHub's process looks nothing like Jira's, which looks nothing like Slack's.
It'd be a nice idea to have documentation for popular providers at https://docs.agentzharness.ai and add that link on the MCP drawer sheet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing content at docs.agentzharness.ai and the MCP drawer sheet where its links are shown. Document client ID and secret setup for popular providers, then add the documentation link to the drawer; done means users can find both the provider instructions and the linked guide.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100