devs using Auth0 should be able to ask:
45,261 次观看
11 条评论
评论来自 X (Twitter) 上的原帖

@dschenkelman
great work @gyaneshgouraw @bharath31_ @jesstemporal and the rest of the team! if you have feedback or feature requests, let us know!
15 个赞

@RTTS_nyc
API testing of interfaces is critical to determine if they meet requirements for functionality, reliability, performance, and security. Check out RTTS - the automated testing experts since 1996. #API #testautomation #integrationtest
39 个赞

@gching
@auth0 @cursor_ai this is so sick.... gonna add to toolbase
4 个赞

@dschenkelman
@auth0 @cursor_ai
2 个赞

@CoopDville2000
@Guz_MassAdopt @auth0 @cursor_ai 👏🏿👏🏿👏🏿
4 个赞

@EdenEmarco177
@auth0 @cursor_ai Looks 🔥🔥🔥 But wondering how is it different then indexing with mcpdoc your documentation ? :)
3 个赞

@dschenkelman
@auth0 @cursor_ai - we control the output to the IDE, not an intermediary - device flow auth (check out the demo flow) - ability to build remote mcp later - composite tools for specific operations that group API calls - ownership, feedback on the MCP server rather than docs
6 个赞

@stijnhommes
@auth0 @cursor_ai Devs using auth0 need to be fired. You shouldn't reuse credentials to access passkeys or reuse your Google credentials to access other accounts. The best way to protect your data is to have unique credentials for EACH account. Every. Single. Time.
1 个赞

@agidevice
@auth0 @cursor_ai niceee - post your cursor content here I bet the cursor community would love to see this!
1 个赞

@dschenkelman
@auth0 @cursor_ai just did. thanks for the nudge ;)

@Mrmemehead
@auth0 @cursor_ai Woah 🤯 🔥
1 个赞